earlyoom.service: add Conflicts #306
Conversation
There was a problem hiding this comment.
At least on my quick testing with similar drop-in config on Fedora 39 and 40, not including the socket as a conflict caused systemd-oomd.service to be constantly started and stopped every few seconds.
I am not sure if I had manually enabled either or not, but I think better safe than sorry.
earlyoom.service.in
Outdated
| @@ -1,6 +1,7 @@ | |||
| [Unit] | |||
| Description=Early OOM Daemon | |||
| Documentation=man:earlyoom(1) https://github.com/rfjakob/earlyoom | |||
| Conflicts=systemd-oomd.service nohang.service oomd.service | |||
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
|
missing nohang-desktop.service |
Some distros default to systemd oom handling. Mark systemd unit conflict with other oom handlers to prevent incompatibility.
|
IMHO 'Conflicts' option creates unexpected behavior when starting one service stops another. But I don't know which solution is optimal. |
This is not necessarily incompatibility: just one killer will work before the other. |
|
Yeah, not sure about this. Having multiple oom handlers is strange, but can still work. A warning would be enough. Is there a way to have systemd warn about it but not prevent it? |
Some distros default to systemd oom handling. Mark systemd unit conflict with other oom handlers to prevent incompatibility.