Lennart Poettering
b2d6bb5b34
Let's inform the the supervisor about various happenings of our service manager, specifically the boot milestones we reach. We so far have only a singular READY=1 message, to inform about bootup completion. But sometimes it is interesting to have something for finegrained, in particular something that indicates optional components that have been activated. Usecase for this: in a later PR I intend to introduce a generic "ssh.target" that is supposed to be activated when SSH becomes available on a host. A supervisor (i.e. a VMM/hypervisor/container mgr/…) can watch for that, and know two things: 1. that SSH is generally available in the system 2. when it is available In order to not flood the supervisor with events I only send these out for target units. We could open this up later, in theory, but I think it makes sense to tell people instead to define clear milestone target units if they want a supervisor to be able to track system state.
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.