From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 12 15:00:22 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4031C16A556 for ; Tue, 12 Apr 2005 15:00:22 +0000 (GMT) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1563043D49 for ; Tue, 12 Apr 2005 15:00:22 +0000 (GMT) (envelope-from bugs@pu.net) Received: from pu.net ([24.1.141.241]) by comcast.net (rwcrmhc13) with ESMTP id <2005041215002101500gvo83e>; Tue, 12 Apr 2005 15:00:21 +0000 Received: (from bugs@localhost) by pu.net (8.13.3/8.11.6) id j3CF0JEI033780 for freebsd-hackers@freebsd.org; Tue, 12 Apr 2005 10:00:19 -0500 (CDT) (envelope-from bugs) From: Mark Hittinger Message-Id: <200504121500.j3CF0JEI033780@pu.net> To: freebsd-hackers@freebsd.org Date: Tue, 12 Apr 2005 10:00:10 -0500 (CDT) X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Wed, 13 Apr 2005 16:22:14 +0000 Subject: re: kernel killing processes when out of swap X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Apr 2005 15:00:22 -0000 I've often wondered why swap doesn't have a root-only x% like the file system. Once the swap used reached 100% user processes would bomb but a root process could go ahead and use the secret x%. Another idea would be to have multiple swap files and implement a way to restrict one swap area to a specific GID (say wheel). While on the issue we could also reserve a range of process ID's for wheel group only. To always be able to log on and un-wedge a system would be most convenient. Later Mark Hittinger bugs@pu.net