Date: Tue, 18 Mar 2003 18:16:00 -0800 From: Wes Peters <wes@softweyr.com> To: Garance A Drosihn <drosih@rpi.edu>, "Daniel C. Sobral" <dcs@tcoip.com.br> Cc: Juli Mallett <jmallett@FreeBSD.org>, Eivind Eklund <eivind@FreeBSD.org>, Mike Silbersack <silby@silby.com>, David Schultz <das@FreeBSD.org>, src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/vm ... SIGDANGER Message-ID: <200303181816.00023.wes@softweyr.com> In-Reply-To: <p05200f2aba97e388a185@[128.113.24.47]> References: <200303122313.h2CNDHMU046431@repoman.freebsd.org> <3E720B5B.8090200@tcoip.com.br> <p05200f2aba97e388a185@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 14 March 2003 12:00, Garance A Drosihn wrote: > > http://nscp.upenn.edu/aix4.3html/aixbman/baseadmn/pag_space_under.htm > > When the number of free paging-space blocks falls below a > threshold known as the paging-space warning level, the system > informs all processes (except kprocs) of this condition by > sending the SIGDANGER signal. > > If the shortage continues and falls below a second threshold > known as the paging-space kill level, the system sends the > SIGKILL signal to processes that are the major users of > paging space and that do not have a signal handler for the > SIGDANGER signal Oh, that's clever. Obviously if you install a handler for SIGDANGER you're telling the system you don't want to get whacked in low memory situations. I'd certainly like to see that behavior duplicated if someone does get around to implemented SIGDANGER. (Sorry, I'm catching up on email from a disconnected weekend and you've just stumbled across a pet project from work here.) -- "Where am I, and what am I doing in this handbasket?" Wes Peters wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200303181816.00023.wes>