From owner-freebsd-current Tue May 8 14:26: 7 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 2861E37B422 for ; Tue, 8 May 2001 14:26:04 -0700 (PDT) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id XAA58345; Tue, 8 May 2001 23:26:01 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: tlambert2@mindspring.com Cc: Dennis Glatting , Kris Kennaway , freebsd-stable@frebsd.org, freebsd-current@FreeBSD.ORG Subject: Re: pgm to kill 4.3 via vm References: <20010507112937.V47835-100000@btw.plaintalk.bellevue.wa.us> <3AF821C9.113680F1@mindspring.com> From: Dag-Erling Smorgrav Date: 08 May 2001 23:26:00 +0200 In-Reply-To: <3AF821C9.113680F1@mindspring.com> Message-ID: Lines: 28 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert writes: > A number of operating systems will allow programs to be > parked "precious". In AIX, this is done by establishing > a signal handler for the resource starvation condition; > programs without the handler "just die". Programs with > the handler are permitted to shut down gracefully. A > "precious" program, such as "init" or the swapper, etc., > just ignore the signal, and reestablish the handler (if > they suffer from SVR3 signal semantics, and can't do it > automatically). Yes. In fact, the new signal stuff was written as a consequence of a previous round of this dicussion, where somebody pointed out that we couldn't implement this because we already had 32 signals, and that the old signal code didn't support more than 32 signals. Now that this is no longer an issue, I wouldn't mind seeing this implemented... But you need to start signalling some yards from the edge of the cliff instead of waiting until you stand at the brink, so your apps get a fighting chance to catch and handle the signal. You might want two signals, actually - one that defaults to SIG_IGN (but some apps may want to catch it and start GCing to play nice with their brethren), and one triggered a little later that kills any process that doesn't catch it. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message