From: Frank van Maarseveen <F.vanMaarseveen@inter.NL.net>
To: Chris Swiedler <chris.swiedler@sevista.com>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>,
Rik van Riel <riel@conectiva.com.br>
Subject: Re: [PATCH] protect processes from OOM killer
Date: Tue, 7 Nov 2000 22:44:33 +0100 [thread overview]
Message-ID: <20001107224433.C883@iapetus.localdomain> (raw)
In-Reply-To: <NDBBIAJKLMMHOGKNMGFNMEADCPAA.chris.swiedler@sevista.com>
In-Reply-To: <NDBBIAJKLMMHOGKNMGFNMEADCPAA.chris.swiedler@sevista.com>; from chris.swiedler@sevista.com on Tue, Nov 07, 2000 at 11:19:37AM -0500
On Tue, Nov 07, 2000 at 11:19:37AM -0500, Chris Swiedler wrote:
> Here's a small patch to allow a user to protect certain PIDs from death-
> by-OOM-killer. It uses the proc entry '/proc/sys/vm/oom_protect'; echo the
> PIDs to be protected:
>
> echo 1 516 > /proc/sys/vm/oom_protect
Hmm, I'd prefer "echo 1 >/proc/516/oom_protect". Guess that's
out of the question because only /proc/sys should be used for
setting parameters?
Then maybe /proc/sys/proc should be populated so we can do
"echo 1 >/proc/sys/proc/516/oom_protect".
--
Frank
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-07 21:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-07 16:19 [PATCH] protect processes from OOM killer Chris Swiedler
2000-11-07 20:47 ` Ingo Oeser
2000-11-07 21:44 ` Frank van Maarseveen [this message]
2000-12-02 2:20 ` Path: for oom_kill.c hugang
2000-12-04 16:57 ` Rik van Riel
2000-12-04 17:52 ` Jeff Epler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20001107224433.C883@iapetus.localdomain \
--to=f.vanmaarseveen@inter.nl.net \
--cc=chris.swiedler@sevista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox