56e8ee55d5
Replace the call to the `end.service` with `systemctl poweroff`, since it seems to cause issues no matter what `--job-mode=` is used: ``` [ 129.070993] testsuite-21.sh[380]: ++ systemctl start --job-mode=flush end.service [ 129.154985] testsuite-21.sh[912]: Failed to start end.service: Transaction for end.service/start is destructive (sysinit.target has 'stop' job queued, but 'start' is included in transaction). [ 129.159636] testsuite-21.sh[912]: See system logs and 'systemctl status end.service' for details. ``` Also, add a "safety net" which bypasses the manager and does the poweroff directly, since sometimes the D-Bus call performed by `systemctl` might timeout (as the manager might be still processing data from the fuzzing): ``` [ 115.776778] sh[894]: + systemctl poweroff --no-block [ 166.164242] testsuite-21.sh[893]: Failed to start transient service unit: Connection timed out [ 166.269289] sh[894]: Call to PowerOff failed: Connection timed out ```
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.