07f4718242
systemd.service(5)’s documentation of `ExecCondition=` uses “failed” with respect to the unit active state. In particular the unit won’t be considered failed when `ExecCondition=`’s command exits with a status of 1 through 254 (inclusive). It will however, when it exits with 255 or abnormally (e.g. timeout, killed by a signal, etc.). The table “Defined $SERVICE_RESULT values” in systemd.exec(5) uses “failed” however rather with respect to the condition. Tests seem to have shown that, if the exit status of the `ExecCondition=` command is one of 1 through 254 (inclusive), `$SERVICE_RESULT` will be `exec-condition`, if it is 255, `$SERVICE_RESULT` will be `exit-code` (but `$EXIT_CODE` and `$EXIT_STATUS` will be empty or unset), if it’s killed because of `SIGKILL`, `$SERVICE_RESULT` will `signal` and if it times out, `$SERVICE_RESULT` will be `timeout`. This commit clarifies the table at least for the case of an exit status of 1 through 254 (inclusive). The others (signal, timeout and 255 are probably also still ambiguous (e.g. `signal` uses “A service process”, which could be considered as the actual service process only). Signed-off-by: Christoph Anton Mitterer <mail@christoph.anton.mitterer.name>
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