Re: OOM killer.

Helge Hafting (helgehaf@aitel.hist.no)
Wed, 23 Jan 2002 14:55:36 +0100


Andrey Nekrasov wrote:
>
> Help.
>
> Is it possible to disable VM-killer completely?
Obviously not - it triggers only when there isn't
enough memory to continue. The alternative to a
OOM killer routine is either a kernel that locks up
effectively killing everything, or a kernel that
allocates all memory early requiring a _lot_ more
memory to run at all. (If you had that memory
you wouldn't run out in the first place.)
>
> Or make it not kill some critical tools. I want, for example, that
> in any situation sshd/nfsd/cron remained alive.

The trivial fix is to start sshd/nfsd/cron from /etc/inittab,
similiar to how getty usually starts. They may still get
killed, but init will restart them asap.

Adding a lot of swap is also a good idea - the machine will
merely slow down instead of killing something.

Helge Hafting
-
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/