Ivan Kruglov
566436f1c6
FailureAction=exit propagates the exit status of the unit's main process. When there is none, emergency_action() left m->return_value at its initial 0, so the manager exited 0 for a unit that failed. Whoever supervises it, e.g. a container manager, then can't tell this apart from an orderly shutdown. There is no status to propagate whenever the unit type has no notion of a main process (only .service has), or the unit failed before any of its processes ran, say because its cgroup couldn't be created. StartLimitAction= and JobTimeoutAction= never have one at all. Fixes: https://github.com/systemd/systemd/issues/43645
System and Service Manager
Details
Most documentation is available on systemd's website.
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