Lines Matching refs:own
58 different processes managing them. However, only a single process should own a
95 various controllers each get their own cgroup file system mounted to
96 `/sys/fs/cgroup/<controller>/`. On top of that systemd manages its own cgroup
146 they might contain a sub-tree of their own managed by something else, made
186 its own below that.
226 hierarchy (in unified and hybrid mode) as well as on systemd's own private
249 both systemd and your own manager would create/delete cgroups below the slice
252 So, if you want to do your own raw cgroups kernel level access, then allocate a
317 2. �� The *i-like-islands* option. If all you care about is your own cgroup tree,
340 service's unit file and you are done and have your own sub-tree. In fact, #2 is
413 of a host systemd which wants to run a systemd as its own container payload
428 each of your containers will have its own systemd-managed unit and hence
454 1. �� Never create your own cgroups below arbitrary cgroups systemd manages, i.e
456 own cgroups below the root cgroup ��. That's owned by systemd, and you will
458 yours. Get your own delegated sub-tree, you may create as many cgroups there
467 attributes of cgroups you created in your own delegated sub-tree, but the