3 ms·

https://github.com/systemd/systemd/blame/e8dc52766e1fdb4f8c09c3ab654d1270e1090c8d/src/oom/oomd-manager.c#L409 https://github.com/systemd/systemd/blame/e8dc52766

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.