Can a process be made immune to out-of-swap-space kills?

Giorgos Keramidas keramida at ceid.upatras.gr
Sun Oct 30 09:50:38 PST 2005


On 2005-10-30 00:21, Doug Lee <dgl at 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 at 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 :)



More information about the freebsd-questions mailing list