News for hackers. Stuff that matters.
Re:I've now disabled systemd-oomd on my Fedora desktops by xg15 on Wednesday December 07, 2022 @11:40AM (#33896533)
Dumb question: why is this a thing at all if the kernel oom killer already exists? Doesn't this effectively do the same as the existing oom killer, but worse?
Re:I've now disabled systemd-oomd on my Fedora desktops by takluyver on Wednesday December 07, 2022 @12:40PM (#33897430)
I believe the kernel OOM killer only fires when you're completely out of memory. But it's not unusual for swap thrashing to make the system unusable before that, forcing the user to either try to kill a likely culprit by hand, or hold down the power button.

systemd-oomd (and earlyoom, which Fedora used for a couple of releases before switching) try to detect that you're running out of RAM before the system becomes unusable, and kill a big memory user. It periodically killed Firefox before I bought some more RAM, which was a pain, but less of a pain than hard-rebooting the laptop.

The plans for Fedora to do this are public pages:

https://fedoraproject.org/wiki/Changes/EnableEarlyoom https://fedoraproject.org/wiki/Changes/EnableSystemdOomd

Re:I've now disabled systemd-oomd on my Fedora desktops by dinosaurdynasty on Wednesday December 07, 2022 @12:12PM (#33897022)
Iirc, systemd-oomd comes from oomd which comes from Facebook who had issues with the kernel oom killer. (The kernel oom killer, especially with slow swap, can also take ages to activate, which means you're just down the entire time, and it's better to kill stuff more often than to sometimes freeze.)
Re:I've now disabled systemd-oomd on my Fedora desktops by freedomben on Wednesday December 07, 2022 @12:36PM (#33897355)
I've had real-world downtime as a result of exactly this. The kernel OOM often takes forever to kick in. Like 10 to 15 minutes is not uncommon.

The most facepalm one was somebody uploaded their `.vimrc` which had a bug that infinitely recursed the parent directory loading ctags until it gobbled up all available memory and crashed. So every time he opened vim, it started about a 40 second timer of doom unless vim was exited before memory exhausted. Took forever to figure it out too, because he often only opened files for 10 seconds or less, short enough not to trigger the OOM.

Re:I've now disabled systemd-oomd on my Fedora desktops by josephcsible on Wednesday December 07, 2022 @11:57AM (#33896793)
Yes it does. Basically everything under the systemd umbrella does the same thing as something that already existed (remember that we had perfectly good Linux boxes before its release in 2010), but worse than the old thing.
Re:I've now disabled systemd-oomd on my Fedora desktops by Avamander on Thursday December 08, 2022 @10:46AM (#33909099)
I have serious doubts about people's familiarity with the alternatives if they say something like this.
Re:I've now disabled systemd-oomd on my Fedora desktops by kaba0 on Wednesday December 07, 2022 @05:21PM (#33901184)
Is it really mentally healthy to hate to this degree a goddamn free, libre, open-source project?
Re:I've now disabled systemd-oomd on my Fedora desktops by hansvm on Thursday December 08, 2022 @11:32AM (#33909816)
Their post seemed pretty tame. No evocative emotions or deity-assisted emphasis. They just said that between the available free, libre, open-source projects they prefer what they had before -- akin to saying they like to install qutebrowser rather than firefox.
Re:I've now disabled systemd-oomd on my Fedora desktops by josephcsible on Wednesday December 07, 2022 @05:56PM (#33901563)
It's not like systemd gave us our freedom. The things it replaced were also FLOSS.