public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Swiedler <ceswiedler@mindspring.com>
To: andreas <andihartmann@freenet.de>,
	Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [2.4.18] Security: Process-Killer if machine get's out of memory
Date: Sun, 24 Mar 2002 10:58:28 -0500	[thread overview]
Message-ID: <3C9DF7A4.5000502@mindspring.com> (raw)
In-Reply-To: <3C9DC1F5.6010508@athlon.maya.org>

andreas wrote:
> Hello all,
> 
> I've got a basic question:
> Would it be possible to kill only the process which consumes the most 
> memory in the last delta t?
> Or does somebody have a better idea?

I had a patch for 2.4.something which would allow you to configure which 
processes were killed first by the OOM killer. You basically gave 
processes an oom_nice value, either by pid or process name, and that was 
  taken into account by the oom killer. You could also protect a process 
completely from the oom killer, which would be good to do for your sshd 
process in the example you give.

Look at http://www.uwsg.iu.edu/hypermail/linux/kernel/0011.1/0453.html

chris


  parent reply	other threads:[~2002-03-24 15:56 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-24 12:09 [2.4.18] Security: Process-Killer if machine get's out of memory andreas
     [not found] ` <3C9DC6D0.3080606@wanadoo.fr>
2002-03-24 13:24   ` Andreas Hartmann
     [not found]     ` <3C9DD653.8090701@wanadoo.fr>
2002-03-24 13:36       ` Andreas Hartmann
2002-03-24 13:30 ` Rik van Riel
2002-03-24 14:08   ` Andreas Hartmann
2002-03-24 16:54     ` Alan Cox
2002-03-24 16:59       ` Andreas Hartmann
     [not found]     ` <3C9E48B8.9080707@ngforever.de>
2002-03-24 22:23       ` Andreas Hartmann
2002-03-24 15:58 ` Chris Swiedler [this message]
2002-03-24 16:57 ` Alan Cox
2002-03-24 16:59   ` Roy Sigurd Karlsbakk
2002-03-24 17:45     ` Rik van Riel
2002-03-24 17:57       ` Christian Bornträger
2002-03-24 18:01         ` Rik van Riel
2002-03-24 18:03         ` Bernd Petrovitsch
2002-03-24 18:23         ` Alan Cox
2002-03-24 18:37         ` Andreas Hartmann
2002-03-24 18:20     ` Alan Cox
2002-03-24 19:20     ` Itai Nahshon
2002-03-24 17:24   ` Andreas Hartmann
2002-03-24 18:22     ` Alan Cox
2002-03-24 18:23       ` Mr. James W. Laferriere
2002-03-24 19:49         ` Alan Cox
2002-03-24 19:48           ` Mr. James W. Laferriere
2002-03-24 20:39             ` Alan Cox
2002-03-24 18:32       ` Andreas Hartmann
2002-03-24 19:50         ` Alan Cox
2002-03-24 20:43           ` Paul P Komkoff Jr
2002-03-25 15:09           ` Rok Papež
2002-03-26 20:24           ` dean gaudet
2002-03-26 23:47             ` Alan Cox

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=3C9DF7A4.5000502@mindspring.com \
    --to=ceswiedler@mindspring.com \
    --cc=andihartmann@freenet.de \
    --cc=linux-kernel@vger.kernel.org \
    /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