From owner-cvs-src Fri Mar 14 8:40:32 2003 Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F8AE37B401; Fri, 14 Mar 2003 08:40:29 -0800 (PST) Received: from smtp2.server.rpi.edu (smtp2.server.rpi.edu [128.113.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED79043FA3; Fri, 14 Mar 2003 08:40:27 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp2.server.rpi.edu (8.12.8/8.12.7) with ESMTP id h2EGeQWG018165; Fri, 14 Mar 2003 11:40:26 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20030314101857.A98861@FreeBSD.org> References: <200303122313.h2CNDHMU046431@repoman.freebsd.org> <20030312175458.J32334@odysseus.silby.com> <20030313005115.GA11794@HAL9000.homeunix.com> <20030313154226.X682@odysseus.silby.com> <20030314012954.A42430@FreeBSD.org> <20030314101857.A98861@FreeBSD.org> Date: Fri, 14 Mar 2003 11:40:25 -0500 To: Juli Mallett , Eivind Eklund From: Garance A Drosihn Subject: Re: cvs commit: src/sys/vm ... SIGDANGER Cc: Mike Silbersack , David Schultz , src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.28 Sender: owner-cvs-src@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 10:18 AM -0600 3/14/03, Juli Mallett wrote: >* De: Eivind Eklund [ Data: 2003-03-14 ] > > > > Having had as my workstation a FreeBSD machine with X, netscape, > > and too little RAM, I think it would be very useful for some > > situations. You have no idea how annoying it is when netscape > > eats all your memory and FreeBSD decide that the solution to > > this is to kill *X*. > >I've had that happen for me (though the combinations required are a >lot lower, as my RAM is a lot lower :>), and that's why I started >looking into this. ... > >Basically I was adding a new signal, SIGVM (or SIGNOMEM), and the >semantics were as such: AIX (and maybe some other systems?) have a signal called SIGDANGER, which is meant for this kind of situation. If we implement some new signal, then perhaps it would be good to use that signal name and mimic their implementation of it. This has been talked about in the past, but has stalled out because there was "no room for new signals" (at the time). Something about a problem with adding any new signal number, although obviously I'm foggy on the details. And I don't know if that issue has been addressed in 5.0. I would like to see this happen. No matter how much memory you have, it would be nice to have some kind of control over which processes will be killed when the system does run out of VM! [mind you, I know about SIGDANGER because several years ago we had some AIX systems which would keep killing 'lpd' if they got low on memory, so I had to use SIGDANGER to protect lpd!] -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-src" in the body of the message