morgan/systemd
1
0
Fork 0
mirror of https://github.com/morgan9e/systemd synced 2026-04-14 00:14:32 +09:00
Code Issues Packages Projects Releases Wiki Activity

docs: Document manual cgroup controller management for Delegate=yes

Browse Source 
This isn't immediately clear, so let's explicitly document this fact.

More context in https://github.com/systemd/systemd/issues/7355.
This commit is contained in:
Daan De Meyer
2025-04-24 22:53:01 +02:00
committed by Luca Boccassi
parent d2502f55a2
commit c2ba4a2864
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/CGROUP_DELEGATION.md
View File

@@ -254,6 +254,12 @@ this is a requirement of threaded cgroups: either a cgroup and all its siblings
are threaded or none –, but systemd expects it to be a regular cgroup. Thus you are threaded or none –, but systemd expects it to be a regular cgroup. Thus you
have to nest a second cgroup beneath it which then can be threaded.) have to nest a second cgroup beneath it which then can be threaded.)
Finally, if you turn on cgroup delegation with `Delegate=yes`, systemd will make
the requested controllers available to your service or scope, but won't actually
enable them. Currently you have to do that manually by writing to
`cgroup.subtree_control` within your delegated cgroup (e.g. write `+memory` to
enable the memory controller).
## Three Scenarios ## Three Scenarios
Let's say you write a container manager, and you wonder what to do regarding Let's say you write a container manager, and you wonder what to do regarding