|
|
Log in / Subscribe / Register

Thanks

Thanks

Posted Nov 24, 2014 19:27 UTC (Mon) by rodgerd (guest, #58896)
In reply to: Thanks by Cyberax
Parent article: Today's Debian technical committee resignation: Ian Jackson

Of course, systemd makes it trivial to mark OOM settings on a per-service basis, too.

to post comments

Thanks

Posted Nov 24, 2014 20:00 UTC (Mon) by Cyberax (✭ supporter ✭, #52523) [Link]

I'm actually thinking that combining socket activation and adjusting OOM killer score to make it _more_ likely to kill sshd is an even better strategy. This way, sshd will be killed first and will free up RAM that is likely wasted.

There's a slight possibility of a livelock when sshd is killed immediately after it's restarted by systemd. Perhaps the "OOMAdjustDelay" setting can be added to systemd?


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds