Bug#727708: systemd as cgroup writer (was: Bug#727708: systemd jessie -> jessie+1 upgrade problems)
* Steve Langasek (firstname.lastname@example.org) [131220 16:57]:
> The design which claims this role for systemd-as-pid-1, and which does not
> adequately address use cases of other existing cgroups consumers in the
> ecosystem (lmctfy, lxc) is broken by design.
> Having a single cgroup writer in userspace is fine. Coupling it to systemd
> in this manner is not.
I would like to understand that topic further, so I have two questions
(to different people):
1. Does systemd (or a part of the systemd project) need to be the
single cgroup writer and if so, why?
2. What problems do arise from there for other parts of the linux