Comment 2 for bug 693264
Revision history for this message
| Stéphane Graber (stgraber) wrote Re: Restricted oom_adj causes job to fail starting completely | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Hmm, ok ... I still think that oom_adj isn't something that should make the whole job to fail as its goal is to make the job more robust (by not getting killed), having it block the whole job seems a bit weird to me.
I guess I won't have much choice then but to update the jobs who show this issue to handle the oom_adj as post-start and not using oom_adj.
Would it be possible to implement some way of having oom_adj being an optional attribute ?
Something like "oom never soft" which would ignore a failure to set oom_adj ?
Or alternatively something like "oom -17 -15" meaning that oom_adj should be -17 but can be set up to -15 if -17 and -16 both fail ?