From: Helge Hafting <helgehaf@aitel.hist.no>
To: Andrey Nekrasov <andy@spylog.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OOM killer.
Date: Wed, 23 Jan 2002 14:55:36 +0100 [thread overview]
Message-ID: <3C4EC0D8.1D8F391F@aitel.hist.no> (raw)
In-Reply-To: <20020123125729.GA5542@spylog.ru>
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
next prev parent reply other threads:[~2002-01-23 13:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-23 12:57 Andrey Nekrasov
2002-01-23 13:55 ` Helge Hafting [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-26 22:37 oom killer mbneto
2005-05-28 2:52 ` John Livingston
2002-02-19 10:02 OOM killer Paco Martinez
2002-02-19 10:34 ` Alan Cox
2002-02-20 19:56 ` Jeffrey Nowland
2002-02-19 14:29 ` Denis Vlasenko
2001-09-27 16:01 Thomas Hood
2001-09-26 17:11 ` Jesper Juhl
2001-09-27 20:52 ` Alex Bligh - linux-kernel
2001-09-26 18:06 ` Jesper Juhl
2001-09-27 23:13 ` Alan Cox
2001-09-28 7:34 ` Jesper Juhl
2001-09-28 7:54 ` Thomas Glanzmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C4EC0D8.1D8F391F@aitel.hist.no \
--to=helgehaf@aitel.hist.no \
--cc=andy@spylog.ru \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®