Zbigniew Jędrzejewski-Szmek
463c301fbb
As a test, it just increases our code coverage in a fake way. When run manually, it can be used to conveniently print what logind thinks about various processes: $ build/test-sd-login sd_pid_get_session(0) → No data available sd_pid_get_unit(0) → user@1000.service sd_pid_get_user_unit(0) → app-ghostty-transient-5088.scope sd_pid_get_machine_name(0) → No such file or directory sd_pid_get_slice(0) → user-1000.slice sd_pid_get_user_slice(0) → app.slice sd_pid_get_owner_uid(0) → 1000 sd_pid_get_cgroup(0) → /user.slice/user-1000.slice/user@1000.service/app.slice/app-ghostty-transient-5088.scope/surfaces/556FAF50BA40.scope $ build/test-sd-login cgroup 1 sd_pid_get_cgroup(1) → /init.scope
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