Date: Sun, 30 Oct 2005 20:50:04 +0200 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: Doug Lee <dgl@dlee.org>, freebsd-questions@freebsd.org Subject: Re: Can a process be made immune to out-of-swap-space kills? Message-ID: <20051030185004.GA7961@flame.pc> In-Reply-To: <20051030042111.GC9983@kirk.dlee.org> References: <20051029203404.GA9983@kirk.dlee.org> <20051029225953.GA56958@flame.pc> <20051030042111.GC9983@kirk.dlee.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2005-10-30 00:21, Doug Lee <dgl@dlee.org> wrote: > On Sun, Oct 30, 2005 at 01:59:53AM +0300, Giorgos Keramidas wrote: > > On 2005-10-29 16:34, Doug Lee <dgl@dlee.org> 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 :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051030185004.GA7961>