Distributions install .wants/, .requires/ and .upholds/ symlinks in /usr/lib/systemd/system/, and PID 1 acts on those exactly like on the ones in /etc/. The install layer doesn't know about that tier at all, so "systemctl is-enabled" reports such units as "disabled" (or "static" for instances) even though they start at boot. On a stock Arch install man-db.timer reports "disabled" while being active. Let's teach find_symlinks_in_scope() about that tier. A dependency symlink below /usr/ now enables the unit, but only one that "systemctl enable" would create, i.e. one in a directory that WantedBy=, RequiredBy= or UpheldBy= in the [Install] section names. Any other such symlink is a static dependency rather than enablement, and reporting the unit as "enabled" because of it would suggest it can be disabled again. remote-cryptsetup.target has WantedBy=multi-user.target, and we install a symlink to it in initrd-root-device.target.wants/, which must not make it report as enabled. Alias= and Also= don't count, as neither results in a dependency symlink. This means "systemctl is-enabled" now exits 0 where it used to exit 1 for these units. Distributions install such symlinks for a number of units, so packaging scripts may notice. Turning them off is a separate matter: disable still can't, which is no worse than before.
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
