4 ms·

> Achievement unlocked: I just had systemd-oomd kill my entire X session for unclear reasons. > Does it log details about the session it killed so I could see

> Achievement unlocked: I just had systemd-oomd kill my entire X session for unclear reasons. > Does it log details about the session it killed so I could see, say, which program was using too much memory? > Nope. > > Systemd-oomd has now been voted off my island. https://github.com/systemd/systemd/blob/v252/src/oom/oomd-manager.c#L409 https://github.com/systemd/systemd/blob/v252/src/oom/oomd-ma... https://github.com/systemd/systemd/blob/v252/src/oom/oomd-manager.c#L532 https://github.com/systemd/systemd/blob/v252/src/oom/oomd-ma... Chris's wiki has now been voted out of my sight.

Avamander 4y ago
To be totally fair, that also happens with the kernel's OOM killer. Sometimes you wish X had been killed, instead of a total freeze or for example LUKS/dm-crypt being unable to allocate memory (and causing way way way worse issues than X being killed).
alyandon 4y ago
https://github.com/systemd/systemd/blame/e8dc52766e1fdb4f8c09c3ab654d1270e1090c8d/src/oom/oomd-manager.c#L409 https://github.com/systemd/systemd/blame/e8dc52766e1fdb4f8c0... Yeah, looks like logging was added 1.5 years ago so hard to take his perspective seriously.
- pengaru 4y ago
  It's also problematic that he doesn't seem to have reported the issue to either his distributor or upstream systemd. If he did, it's not mentioned in his rant. There aren't any links to any bug reports where the developers demonstrably failed to care or anything rant-worthy. Considering systemd-oomd is a relatively new addition to the project, contributed by FB staff, it wouldn't surprise me if there were desktop integration issues yet to be sorted out by the various distros. The post doesn't strike me as made in good faith, seems written by someone with an axe to grind with systemd.