From owner-freebsd-questions@FreeBSD.ORG Sat Oct 29 20:34:09 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C14C16A41F for ; Sat, 29 Oct 2005 20:34:09 +0000 (GMT) (envelope-from dgl@kirk.dlee.org) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [204.127.198.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 955E043D48 for ; Sat, 29 Oct 2005 20:34:08 +0000 (GMT) (envelope-from dgl@kirk.dlee.org) Received: from kirk.dlee.org ([69.143.16.144]) by comcast.net (rwcrmhc12) with ESMTP id <20051029203407014001lom1e>; Sat, 29 Oct 2005 20:34:07 +0000 Received: from kirk.dlee.org (dgl@localhost.dlee.org [127.0.0.1]) by kirk.dlee.org (8.12.11/8.12.11) with ESMTP id j9TKY5WW010119 for ; Sat, 29 Oct 2005 16:34:05 -0400 (EDT) (envelope-from dgl@kirk.dlee.org) Received: (from dgl@localhost) by kirk.dlee.org (8.12.11/8.12.11/Submit) id j9TKY51G010118 for freebsd-questions@freebsd.org; Sat, 29 Oct 2005 16:34:05 -0400 (EDT) (envelope-from dgl) Date: Sat, 29 Oct 2005 16:34:05 -0400 From: Doug Lee To: freebsd-questions@freebsd.org Message-ID: <20051029203404.GA9983@kirk.dlee.org> Mail-Followup-To: Doug Lee , freebsd-questions@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Organization: SSB + BART Group User-Agent: Mutt/1.5.9i Subject: Can a process be made immune to out-of-swap-space kills? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Oct 2005 20:34:09 -0000 Sometimes, I accidentally run something that eats up too much memory and causes the pager to run out of swap space and start shooting down processes to rectify the situation. Sometimes, the process chosen for demolition happens to be `screen.' Since this process sorta manages a whole lot of others and, on being zapped out of existence, leaves many of them running but inaccessible, I find this choice decidedly inconvenient. Is there a way for me to force FreeBSD to leave `screen' (or any other process) alone when selecting something to kill to free memory? Please Cc me any answers. Thanks much. -- Doug Lee dgl@dlee.org http://www.dlee.org SSB + BART Group doug@bartsite.com http://www.bartsite.com "Is your cucumber bitter? Throw it away. Are there briars in your path? Turn aside. That is enough. Do not go on to say, `Why were things of this sort ever brought into the world?'" --Marcus Aurelius