zbyszek added a new comment to an issue you are following:
``
This seems to be all based on a misunderstanding — systemd never allowed (*) other
entities to muck around with parts of the cgroup hierarchy that it manages, including
slice units. The difference with systemd-238 is that it's slightly clearer about this,
and e.g. setting Delegate before would be silently ignored before and results in an error
now. See
https://github.com/systemd/systemd/issues/8645 for another discussion of this.
In particular, .slice units would be create "on demand", i.e. when another
.service/.slice/whatever nested unit was requested, the parent .slice would be created,
and destroyed when systemd thinks it's not needed any more.
(*) "allow" needs a clarification: there is no enforcement of this, because a
user space process cannot prevent another privileged process from changing the cgroup
hierarchy. So "allow"/"disallow" here is at the level of "please
don't do this" or "you get to keep the pieces".
There's also the option of reverting the systemd commit.
This could be discussed as an option to do this as a hack to get things to work
temporarily, but it's not a long term solution.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/452