Date: Mon, 28 May 2001 16:06:59 -0700 (PDT) From: Matt Dillon <dillon@earth.backplane.com> To: The Hermit Hacker <scrappy@hub.org> Cc: Tom <tom@uniserve.com>, <freebsd-stable@FreeBSD.ORG> Subject: Re: machine hangs when no memory/swap left ... Message-ID: <200105282306.f4SN6xG13452@earth.backplane.com> References: <Pine.BSF.4.33.0105281941440.436-100000@mobile.hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
:On Mon, 28 May 2001, Tom wrote:
:>
:> On Mon, 28 May 2001, The Hermit Hacker wrote:
:>
:> > stupid question, but shouldn't there be a mechanism to prevent that?
:> > something to crash the process or somethign when the machine runs out of
:> > virtual memory?
:>
:> It has always been my experience that it does. Basically the process
:> that requests memory that doesn't exist, is killed.
:
:Any way of turning this feature on? :) I have a hung, remote machine
:right now that is out of memory ... we caught it "just about to do it"
:earlier today, and it actually did it this evening :(
:
:This aft, it was two 400Meg httpsd processes that brought her close, so
:I'm guessing similar this evening did her in ...
This is a known bug in -stable and -current. The kernel is supposed to
kill the bigger processes but locks up before it gets the chance.
It's probably fairly easy to fix, but I haven't had time to delve into it.
In regards to runaway processes... that's why you set reasonable
resource limits. So a runaway process dies without taking the system down
with it.
-Matt
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200105282306.f4SN6xG13452>