Frantisek Sumsal
fab73dad84
So the multiple-machines tests run last to avoid a race where the checked signal would get ignored while the stub init is still processing the previous signals: [ 17.380417] testsuite-13.sh[376]: + machinectl reboot long-running long-running long-running [ 17.389888] systemd-nspawn[495]: ++ touch /reboot [ 17.390904] testsuite-13.sh[376]: + rm -f /var/lib/machines/long-running/trap [ 17.393937] testsuite-13.sh[376]: + machinectl kill --signal=SIGTRAP --kill-whom=leader long-running [ 17.408905] testsuite-13.sh[376]: + timeout 10 bash -c 'while ! test -e /var/lib/machines/long-running/trap; do sleep .5; done' [ 27.413210] testsuite-13.sh[376]: + at_exit ... [ 27.993376] testsuite-13.sh[373]: + echo 'Subtest /usr/lib/systemd/tests/testdata/units/testsuite-13.machinectl.sh failed'
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.