1da030e6e1
We use StandardOutput=journal+console for integration test units to make sure the output from the test ends up on both the serial console and in the journal. Unfortunately this only works for messages written to stdout/stderr of the test service. All journal messages logged by systemd tools will only end up in the journal and not on the serial console. This makes test failures harder to debug than needed because developers have to fetch the journal to figure out the actual error that was logged by any systemd tool that failed when invoked from the integration test script. To fix this, let's unset $JOURNAL_STREAM for the integration test units. This forces all output to go through stdout, which will make journald forward it to the console and save it in the journal.
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, 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