Killing the broker is destructive well beyond the units under test: nothing reconnects to the new one, so logind for instance keeps running with org.freedesktop.login1 unowned for the rest of the boot. As a subtest of TEST-23-UNIT-FILE that leaked into everything running after it, and statedir.sh, the first one to start user@0.service, then spent 25s per logind property in user-runtime-dir and, where pam_systemd can't use Varlink, blocked in CreateSession() past user@.service's 90s TimeoutStartSec and failed — with the failure pointing at a subtest that has nothing to do with the bus. In its own test the damage dies with the machine.
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
