The current arrangement of service and socket units is sort of all over the place. Let's clean it up a little, roughly following the principles below: - socket units have implicit ordering deps (not to be confused with default ones which are subject to DefaultDependencies=) before associated service, so drop any explicit After= - If socket can be enabled, remember to link to it in service via Also= and Sockets= (the latter replaces Wants=). If the service Requires= socket however, Sockets= is omitted. - If socket is statically enabled, no need for service to pull it in - machined
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
