Lines Matching refs:slice

162 3. �� The `.slice` unit type. Units of this type do not directly contain any
169 be moved around though, i.e. assigned to a different slice if needed.
171 The naming of slice units directly maps to the cgroup tree path. This is not
172 the case for service and scope units however. A slice named `foo-bar-baz.slice`
173 maps to a cgroup `/foo.slice/foo-bar.slice/foo-bar-baz.slice/`. A service
174 `quux.service` which is attached to the slice `foo-bar-baz.slice` maps to the
175 cgroup `/foo.slice/foo-bar.slice/foo-bar-baz.slice/quux.service/`.
177 By default systemd sets up four slice units:
179 1. `-.slice` is the root slice. i.e. the parent of everything else. On the host
182 2. `system.slice` is where system services are by default placed, unless
185 3. `user.slice` is where user sessions are placed. Each user gets a slice of
188 4. `machines.slice` is where VMs and containers are supposed to be
246 only. It's expressly not available on slice units. Why? Because slice units are
248 to them. If we'd allow delegation on slice units then this would mean that
249 both systemd and your own manager would create/delete cgroups below the slice
374 `.slice` components too, otherwise the hierarchies will start being orthogonal
462 2. �� Don't attempt to set `Delegate=` in slice units, and in particular not in
463    `-.slice`. It's not supported, and will generate an error.
482 5. ⚡ Currently, the algorithm for mapping between slice/scope/service unit
485    local logic of translating cgroup paths to slice/scope/service names in your