As of some time recently there is a separate flag that supersedes
oom_adj called I believe oom_unkillable, which appears to be set
properly, so this is no longer an issue and can be closed.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe".
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
[Paul Nienaber]
> Under no circumstances should init have its oom_adj set to anything
> other than -17. watchdog and other facilities have this set
> properly, it seems.
I fail to understand your report. Can you provide more information
and perhaps a patch proposal? Is there some new behaviour
Package: sysvinit
Version: 2.88dsf-11
Severity: critical
Justification: causes serious data loss
*** Please type your report below this line ***
Under no circumstances should init have its oom_adj set to anything
other than -17. watchdog and other facilities have this set properly,
it seems.
4 matches
Mail list logo
