Messages in this thread | | | Subject | Re: [PATCH] oom killer (Core) | From | Thomas Gleixner <> | Date | Fri, 03 Dec 2004 22:20:22 +0100 |
| |
On Fri, 2004-12-03 at 15:41 +0100, Helge Hafting wrote: > The case of OOM killed sshd is fixable without touching the kernel: > Make sure sshd is started from init, init will then restart sshd whenever > it quits for some reason. This will get you your essential sshd back > assuming the machine is still running and the OOM killer managed > to free up some memory by killing some other processes. > > One might still wish for better OOM behaviour, but it is a case > where something has to give. >
Hey, are you kidding ?
2.4 lets me not in, because the fork of sshd fails. How do you fix this with changing the userspace ?
2.6 oom is plain buggy
I have no problem to help myself, but I want to get this fixed in a reliable way which meets the comment in oom_kill.c: "least surprise"
tglx
- 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/
| |