Lennart Poettering
9752a9ef8f
On kernels lacking CLONE_INTO_CGROUP sd-executor is forked into the service manager's cgroup, logs a few messages from there, and only then attaches itself to the unit's cgroup and connects stdout/stderr to journald. Since we cache client metadata per PID and only refresh it after 1s, log output on such a stream was attributed to init.scope rather than to the unit, and hence "journalctl -u" (and thus "systemd-run -v", "systemctl -v start", "systemctl -v wait") would not show it. Hence, if a stream tells us the unit it belongs to, and that doesn't match what we have cached, refresh the cached data. (cherry picked from commit 44a9316bf49967164567a7c716b79af7edf53d03)
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