0310b2a60b
The current logic is a bit complex how systemd-run units are called. It used to be just the unique ID of the dbus connection. Which was nice, since its system-widely, uniquely assigned to us. But this didn't work out well, due to direct connections to PID 1 and due to soft reboots. We nowadays have a better ID to use though, with nicer properties: the kernel manages a pidfd ID for every process after all, and it's globally unique, for any process, and regardless of soft reboots. Hence use that for naming preferably, and just keep one branch with a randomized name as fallback.
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