RE: Killing/balancing processes when overcommited

From: Rik van Riel (riel@conectiva.com.br)
Date: Fri Sep 13 2002 - 17:44:56 EST


On 13 Sep 2002, Timothy D. Witham wrote:

> In this case the offense is asking for more memory. So it is the
> process that asks for more memory that goes away. Again sometimes it
> will be an innocent bystander but hopefully it will eventually be the
> process that is causing the problem.

If you kill the process that requests memory, the sequence often
goes as follows:

1) memory is exhausted

2) the network driver can't allocate memory and
   spits out a message

3) syslogd and/or klogd get killed

Clearly you want to be a bit smarter about which process to kill.

regards,

Rik

-- 
Bravely reimplemented by the knights who say "NIH".

http://www.surriel.com/ http://distro.conectiva.com/

Spamtraps of the month: september@surriel.com trac@trac.org

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Sun Sep 15 2002 - 22:00:35 EST