In several Ubuntu CI jobs I noticed timeouts in TEST-69, which are apparently caused by a very stubborn bash/login process: $ journalctl -o short-monotonic --no-hostname --file artifacts/TEST-69-SHUTDOWN.journal [ 2011.698430] systemd[1]: shutdown.target: starting held back, waiting for: veritysetup.target [ 2011.698473] systemd[1]: sysinit.target: stopping held back, waiting for: user@0.service [ 2045.884982] systemd[1]: systemd-oomd.service: Got notification message from PID 54 (WATCHDOG=1) [ 2071.576424] systemd[1]: Received SIGCHLD from PID 65 (bash). [ 2071.576941] systemd[1]: Child 65 (bash) died (code=killed, status=1/HUP) [ 2071.577026] systemd[1]: session-13.scope: Child 65 belongs to session-13.scope. [ 2071.577100] systemd[1]: session-13.scope: cgroup is empty [ 2071.577249] systemd[1]: session-13.scope: Deactivated successfully. $ journalctl -o short-monotonic --no-hostname --file artifacts/TEST-69-SHUTDOWN.journal _PID=65 [ 3038.661488] login[65]: ROOT LOGIN on '/dev/pts/0' Since, in this case, we really care only about the actual shutdown, let's shorten the service stop/abort timeouts to let systemd SIGKILL all remaining processes in the 60s `expect` window.
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 or join our IRC channel.
Stable branches with backported patches are available in the stable repo.
