Re: [why oom_adj does not work] Re: Linux killed Kenny, bastard!

[Evgeniy Polyakov]

On Sat, Jan 17, 2009 at 03:12:49PM +0100, Bodo Eggert (7eggert@xxxxxx) wrote:
> > > > This does not work if processes are short-living and are spawned by the
> > > > parent on demand.
> > > 
> > > They will have the same name, too. Your Kenny-killer will fail, too.
> > 
> > It is not always the case, processes start executing different binaries
> > and change the names, that's at least what I observed in the particular
> > root case of the discussion.
> 
> In that case, you can use a wrapper script.

That may be a solution, except that not very convenient, since there may
be really lots of executables and cooking up a special script for
everyone will not scale well.

> > There could be lots of heuristics applied for the different cases, but
> > without changing the application, they are somewhat limited to
> > long-living processes only. There are really lots of cases when it does
> > not stand.
> 
> If it's short-lived enough, the processes will out-die the OOM-Killer.
> You can only win by by suspending or killing the factory.

No, admin will limit/forbid the connection from the DoSing clients,
server must always live to handle proper users.

-- 
	Evgeniy Polyakov
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/