Chris Down
e93511b10e
oomd_cgroup_kill_mark() currently returns 0 on all non-error paths. But the manager only logs that it marked for killing on `if (r > 0)`, which is thus unreachable. Changing it to `r >= 0` would also be wrong, because then we would log on no-op paths. So let's fix this by making the return value express what actually happened: - < 0: failure to queue the kill state - 0: no new mark was created (already queued or dry-run) - > 0: a new kill state was queued
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list, join our IRC channel #systemd on libera.chat or Matrix channel
Stable branches with backported patches are available in the stable repo.
We have a security bug bounty program sponsored by the Sovereign Tech Fund hosted on YesWeHack
Repositories with distribution packages built from git main are available on OBS, and also repositories with packages built from the latest stable release