OOM-killer prevention for master kdeinit process
Lubos Lunak
l.lunak at suse.cz
Mon Aug 7 10:18:29 BST 2006
On Friday 04 August 2006 22:15, Oswald Buddenhagen wrote:
> On Fri, Aug 04, 2006 at 09:27:22PM +0200, Thomas Zander wrote:
> > On Friday 4 August 2006 20:59, Oswald Buddenhagen wrote:
> > > > Any objections to commit?
> > >
> > > yes. you are essentially creating a blank check for any application to
> > > "escape" oom-killing,
> >
> > Could you explain why changing this one process would have that effect?
>
> uhm, well, actually, it's not that bad, as EXECUTE is hard-coded, making
> it effectively my second case.
What second case, setuid KApplication? There's no setuid KApplication. Or do
you still see some other problem with it?
> otoh, hard-coding paths in binaries is another thing that *should* be
> avoided (not that *yet another* case would actually hurt ...).
Stupid OOM-killer should be probably avoided more.
--
Lubos Lunak
KDE developer
---------------------------------------------------------------------
SuSE CR, s.r.o. e-mail: l.lunak at suse.cz , l.lunak at kde.org
Drahobejlova 27 tel: +420 2 9654 2373
190 00 Praha 9 fax: +420 2 9654 2374
Czech Republic http://www.suse.cz/
More information about the kde-core-devel
mailing list