I just wanted to give people a heads up that systemd-oomd as configured in Fedora out the box "doesn't work well" on build systems.
Why? If if sees something using 90+% of the system memory, it will terminate it. "It" in this case is the whole user cgroup/session. On the autobuilder this means it doesn't just take out some subcomponent of the build, it takes out the buildbot-worker and everything it has started, i.e. all the builds. Worse, when it does this you don't get any logs about what it actually killed, just that a session using 90% of the system memory was destroyed. Since our autobuilder workers just run builds, we really don't mind then using most of the system resources. We're therefore disabling this "service". I thought others may want to be aware though. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#166215): https://lists.openembedded.org/g/openembedded-core/message/166215 Mute This Topic: https://lists.openembedded.org/mt/91380681/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
