Anita Zhang
e51237253e
When there are multiple ExecStop= statements, the next command would continue to run even after TimeoutStopSec= is up and sends SIGTERM. This is because, unless Type= is oneshot, the exit code/status would evaluate to SERVICE_SUCCESS in service_sigchld_event()'s call to is_clean_exit(). This success indicates following commands would continue running until the end of the list is reached, or another timeout is hit and SIGKILL is sent. Since long running processes should not be invoked in non-SERVICE_EXEC_START commands, consider them for EXIT_CLEAN_COMMAND instead of EXIT_CLEAN_DAEMON. Passing EXIT_CLEAN_COMMAND to is_clean_exit() evaluates the SIGTERM exit code/status to failure and will stop execution after the first timeout is hit. Fixes #11431
systemd - System and Service Manager
Details
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 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 or join our IRC channel.
Stable branches with backported patches are available in the stable repo.