CLI tools may be used in a script. E.g., a script for monitoring a service may use `systemctl`. Previously, if the kernel command line has e.g. systemd.log-level=debug, then systemctl in the script produces debugging logs when the script is invoked by a .service unit, but does not when the script is running in a terminal. Then, https://github.com/systemd/systemd/pull/18281#discussion_r561697482, > I expect users to be (negatively) surprised. In the previous commit, $SYSTEMD_EXEC_PID= is introduced. Then, we can now detect whether a command is directly invoked by systemd or through a script. Let's skip reading the kernel command line when a command is invoked through a script.
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 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 or join our IRC channel.
Stable branches with backported patches are available in the stable repo.