From owner-freebsd-questions@FreeBSD.ORG Sat Oct 29 23:27:18 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 85BB416A41F for ; Sat, 29 Oct 2005 23:27:18 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from mail.vivodinet.gr (mail3.vivodinet.gr [80.76.39.13]) by mx1.FreeBSD.org (Postfix) with SMTP id 84B2A43D48 for ; Sat, 29 Oct 2005 23:27:16 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: (qmail 28494 invoked from network); 29 Oct 2005 23:00:05 -0000 Received: from dslcustomer-222-89.vivodi.gr (HELO flame.pc) (83.171.222.89) by 0 with SMTP; 29 Oct 2005 23:00:05 -0000 Received: from flame.pc (flame [127.0.0.1]) by flame.pc (8.13.4/8.13.4) with ESMTP id j9TMxtpI056981; Sun, 30 Oct 2005 01:59:55 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost) by flame.pc (8.13.4/8.13.4/Submit) id j9TMxsvm056980; Sun, 30 Oct 2005 01:59:54 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Sun, 30 Oct 2005 01:59:53 +0300 From: Giorgos Keramidas To: Doug Lee , freebsd-questions@freebsd.org Message-ID: <20051029225953.GA56958@flame.pc> References: <20051029203404.GA9983@kirk.dlee.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051029203404.GA9983@kirk.dlee.org> Cc: Subject: Re: 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 23:27:18 -0000 On 2005-10-29 16:34, Doug Lee wrote: > 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? Hmmm, why are user limits not applied? Wouldn't it be a nicer way to solve the "rogue process" problems?