5346bb499f
Those are rather specialized bits of information, useful mostly for debugging. I use cgls quite often but never had the need to use either of those… But they take up a significant amount of screen real estate, esp. when executed as root: -.slice ├─user.slice (#1683) │ → user.invocation_id: 74b0bd1258c5485eb969016384e0d06a │ → trusted.invocation_id: 74b0bd1258c5485eb969016384e0d06a │ └─user-1000.slice (#6488) │ → user.invocation_id: b0261a14fe74490d9a9d5266c52cceb6 │ → trusted.invocation_id: b0261a14fe74490d9a9d5266c52cceb6 │ ├─user@1000.service … (#6590) │ │ → user.invocation_id: 9e1fb54ad07940d8b92c33c81d169f11 │ │ → user.delegate: 1 │ │ → trusted.invocation_id: 9e1fb54ad07940d8b92c33c81d169f11 │ │ → trusted.delegate: 1 │ │ ├─session.slice (#6874) ... Let's not show them by default, so we can show more cgroups. (Also, on a terminal, we already highlight delegate units via underlining and an ellipsis, so 'user.delegate:1' is redundant.)
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 or join our IRC channel.
Stable branches with backported patches are available in the stable repo.