Re: Protecting processes from the OOM killer

James Antill
2003-02-28T22:03:45Z

Dan Kegel <dank@kegel.com> writes:

> Alan Cox wrote:
> > On Fri, 2003-02-28 at 01:21, Dan Kegel wrote:
> >
> > Everything else is armwaving "works half the time" stuff. By the time
> > the OOM kicks in the game is already over.
>
> Even with overcommit disallowed, the OOM killer is going to run
> when my users try to run too big a job, so I would still like
> the OOM killer to behave "well".

If OOM is called you've overcommitted memory, so this isn't true
... no overcommit == NULL from malloc() etc.

--
# James Antill -- james@and.org
:0:
* ^From: .*james@and\.org
/dev/null