Date: Wed, 22 Sep 1999 10:38:49 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: Nate Williams <nate@mt.sri.com> Cc: Alfred Perlstein <bright@wintelcom.net>, Chuck Robey <chuckr@mat.net>, "Daniel C. Sobral" <dcs@newsguy.com>, Ivan <Ivan.Djelic@prism.uvsq.fr>, freebsd-hackers@FreeBSD.ORG Subject: Re: Out of swap handling and X lockups in 3.2R Message-ID: <199909221738.KAA16257@apollo.backplane.com> References: <Pine.BSF.4.10.9909221227080.312-100000@picnic.mat.net> <Pine.BSF.4.05.9909221024370.6368-100000@fw.wintelcom.net> <199909221727.LAA14290@mt.sri.com>
next in thread | previous in thread | raw e-mail | index | archive | help
How about this - add an 'importance' resource. The lower the number,
the more likely the process will be killed if the system runs out of
resources. We would also make fork automatically decrement the number
by one in the child.
The default would be 1000. The sysadmin could then use login.conf to
lower the hard limit for particular users or user classes, and of course
set a specific limit for particular root-run processes (though, in general,
the daemons will be protected because their children will be more likely
to be killed then they will).
The system would use the importance resource to modify its search for
processes to kill - perhaps use it as a divisor. Or the system could use
it absolutely then kill the biggest process of the N processes sitting
at the lowest importance level.
This also solves the sysad-cant-login problem and the user-is-naughty
problem.
-Matt
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199909221738.KAA16257>