[deleted]
> This leaves the job of administration up to the admin. He should be aware
> of when a program may have sucked up all available memory, and should
> decide when and if to kill that process.
>
> Just as you had to do, personally that look s much better than a hung
> system yeah?
You're right. I understand that the job of the OS is (also) to keep the
system alive in stress conditions (and this is specially true in
corporate networks) but take in account that when you administer a lot
of remote servers, an OOMKiller is not such a bad thing to enable. If
killer kills, eg, sendmail you will be alerted by your normal
alarm/monitoring software and can log in remotely and restart it.
At this time, you could not even log in to do that. It sucks going to
the central site 3am just to press reset (but this is a little OT).
Regards
Dino
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/