Messages in this thread | | | Date | Thu, 12 Sep 2002 09:25:26 +0200 (CEST) | From | Giuliano Pochini <> | Subject | RE: Killing/balancing processes when overcommited |
| |
On 11-Sep-2002 Jim Sibley wrote: > I have run into a situation in a multi-user Linux environment that when > memory is exhausted, random things happen. [...] In a "well tuned" system, > we are safe, but when the system accidentally (or deliberately) becomes > "detuned", oom_kill is entered and arbitrarily kills a process.
It's not difficult to make the kerner choose the right processes to kill. It's impossible. Imagine that when it goes oom the system stops and asks you what processes have to be killed. What do you kill ? I think the only way to save the system it to tell the kernel which are the processes that must not be killed, except in extreme conditions. Probably we do need an oomd that the sysadmin can configure as he likes.
Bye.
- 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/
| |