...with gnome-shell and systemd-oomd being the most active processes (and using up like 25% of the CPU time in idle), this setup doesn't really make sense.
@galaxis So in its default configuration the kernel overcommits memory and kills random programs when programs abuse this. And now the systemd devs added a userspace monitoring tool which tries to prevent the wrong process from getting killed in such situations? The userspace/kernelspace split in the linux community must be running very deep indeed if that's the solution they end up with. (I don't have a horse in this race and don't really care, just an observation from the outside.)
@stsp I assume if the systemd people were prepared to take up and enhance existing solutions for anything, they wouldn't need to reimplement everything they touch from scratch.
It's not something I like personally, even though it did actually solve some longstanding problems on the way...
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!