97754cd14d
So far, machined strictly tracked the "leader" process of a machine, i.e. the topmost process that is actually the payload of the machine. Its runtime also defines the runtime of the machine, and we can directly interact with it if we need to, for example for containers to join the namespaces, or kill it. Let's optionally also track the "supervisor" process of a machine, i.e. the host process that manages the payload if there is one. This is generally useful info, but in particular is useful because we might need to communicate with it to shutdown a machine without cooperation of the payload. Traditionally we did this by simply stopping the unit of the machine, but this is not doable now that the host machined can be used to track per-user machines. In the long run we probably want a more bespoke protocol between machined and supervisors (so that we can execute other commands too, such as request cooperative reboots/shutdowns), but that's for later. Some environments call the concept "monitor" rather than "supervisor" or use some other term. I stuck to "supervisor" because nspawn uses this, and ultimately one name is as good as another. And of course, in other implementations of VM managers of containers there might not be a single process tracking each VM/container. Because of this, the concept of a supervisor is optional.
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