[lkml]   [2002]   [Jan]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectOOM kill in 2.4.18-pre4
Hello again,                                                          

I just happened to try make -j on a too small box. Obviously I ran
into OOM. What I find a bit strange about it is the selection of
processes that got killed.
After reviewing the code in oom_kill.c I must admit I find it kind of
too smart for real live.
In my situation the first thing killed was mozilla, though being
somewhere in the background and not reponsible for the OOM situation.
The next 2 processes killed were my beloved setis. Obviously because
they were nice :-)
And the last thing was the xterm I did make -j.
My personal taste would be that the guy _producing_ the situation
should be punished first, not poor mozilla (only because its big).
I can very well imagine a situation on an (e.g.) oracle server, where
you start just one thing too much and your primary server goal
(oracle) gets kicked out because you did something stupid.
I know Rik would say: your fault ;-)
But, hey, I probably paid for the server and then kernel tells me:
make my day, a*hole...

Guess you know what I mean :-)
Is anybody against making it a bit less intelligent, and more real
live adequate?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:23    [W:0.029 / U:2.616 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site