From owner-cvs-all Fri Mar 14 14:23:41 2003 Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD1FA37B401; Fri, 14 Mar 2003 14:23:38 -0800 (PST) Received: from smtp1.server.rpi.edu (smtp1.server.rpi.edu [128.113.2.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CC6C43F93; Fri, 14 Mar 2003 14:23:37 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp1.server.rpi.edu (8.12.8/8.12.7) with ESMTP id h2EMNZBg025794; Fri, 14 Mar 2003 17:23:36 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Fri, 14 Mar 2003 17:23:34 -0500 To: John Baldwin , Pawel Jakub Dawidek From: Garance A Drosihn Subject: Re: cvs commit: src/sys/vm ... SIGDANGER Cc: cvs-all@FreeBSD.org, cvs-src@FreeBSD.org, src-committers@FreeBSD.org, David Schultz , Eivind Eklund , Juli Mallett , Poul-Henning Kamp , Mike Silbersack , "Daniel C. Sobral" Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.28 Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 4:37 PM -0500 3/14/03, Garance A Drosihn wrote: >Perhaps the problem people have with SIGDANGER, even though it has >in fact been proven to be useful in real-life situations, is that >as implemented by AIX you have to change some source code (maybe >in a variety of programs) to take advantage of it. That is an >interesting point, but perhaps we can solve that. > >How about having the default SIGDANGER signal handler do something >a little more interesting than always ignoring the signal? Perhaps >have the default routine check some process-specific value, and it >(the default signal handler) can decide what to do based on that >value. Then give a system administrator a way to set the value. >say, value 1 = kill process at threshold #1 > 2 = kill process at threshold #2 (& not at #1) > 3 = Only kill process if you're still running out > of space after killing all you could kill at > threshold's #1 and #2. > 4 = if you're still running out of memory after #3, > then just reboot, because it's hopeless... :-) > >To match the AIX behavior of SIGDANGER, the default would be #2. We could even add another value. All the above values could mean "and ignore any program-specified SIGDANGER routine", while a value 0 would exactly match the historical AIX behavior. -- 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-all" in the body of the message