[Pkg-sysvinit-devel] Bug#591854: sysvinit: init oom_adj value set to 0 not -17

Petter Reinholdtsen pere at hungry.com
Tue Aug 10 07:25:18 UTC 2010


severity 591854 important
thanks

[Paul Nienaber]
> After further thought, depending on what is or isn't being set in
> userspace at present, this may be something that should be
> upstreamed to kernel folks, as setting this for init is kind of an
> obvious thing to do even if userspace is dumb and lacks fancy
> start-up infrastructure/etc.  I.e., it should even be set when using
> busybox or whatever.  Thoughts?

It seem to me like it should be the responsibility of the kernel to
protect the init process by default, and not the init process
responsibility to tell the kernel not to kill the PID 1.

Further, as this only affect machines running out of memory and swap,
I believe the severity should at most be important.

I am not quite sure where to reassign it to get input from the kernel
developers, so I hope others can take care of that part.

Happy hacking,
-- 
Petter Reinholdtsen





More information about the Pkg-sysvinit-devel mailing list