From owner-freebsd-questions@FreeBSD.ORG Sun Oct 30 17:50:37 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 E5E4616A422 for ; Sun, 30 Oct 2005 17:50:37 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from kane.otenet.gr (kane.otenet.gr [195.170.0.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id A337A43D60 for ; Sun, 30 Oct 2005 17:50:24 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from flame.pc (patr530-a230.otenet.gr [212.205.215.230]) by kane.otenet.gr (8.13.4/8.13.4/Debian-1) with ESMTP id j9UHoIC0024640; Sun, 30 Oct 2005 19:50:19 +0200 Received: from flame.pc (flame [127.0.0.1]) by flame.pc (8.13.4/8.13.4) with ESMTP id j9UIo41d007985; Sun, 30 Oct 2005 20:50:04 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost) by flame.pc (8.13.4/8.13.4/Submit) id j9UIo4Zx007984; Sun, 30 Oct 2005 20:50:04 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Date: Sun, 30 Oct 2005 20:50:04 +0200 From: Giorgos Keramidas To: Doug Lee , freebsd-questions@freebsd.org Message-ID: <20051030185004.GA7961@flame.pc> References: <20051029203404.GA9983@kirk.dlee.org> <20051029225953.GA56958@flame.pc> <20051030042111.GC9983@kirk.dlee.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051030042111.GC9983@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: Sun, 30 Oct 2005 17:50:38 -0000 On 2005-10-30 00:21, Doug Lee wrote: > On Sun, Oct 30, 2005 at 01:59:53AM +0300, Giorgos Keramidas wrote: > > 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? > > It turns out that the problem is not actually a memory request but a > huge temp file in an MFS filesystem... so maybe I need to figure out > how to limit the size of a mount_mfs so it can't blast processes out > of existence. Ah! That explains why this wasn't caught by the user limits :)