** Changed in: cgmanager (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: systemd (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Hope had been that the kernel's new support for cpuset.effective_cpus
would fix this. Removing a cpu from a parent cgroup or offlining a cpu
would remove it from effective_cpus, but not from cpuset.cpus.
Apparently that's not the case (kernel 3.19.0-10-generic was used for
the test in comment
This bug was fixed in the package cgmanager - 0.35-1ubuntu1
---
cgmanager (0.35-1ubuntu1) vivid; urgency=medium
* 0001-implement-M-to-support-skip-mounting-certain-control.patch:
This doesn't change the default, so may not suffice for powerpc,
but at least offers a
systemd (in the sense of pid 1) doesn't do that. I. e. if you boot with
init=/bin/systemd the only cgroup controller it puts tasks into (by
default) is the systemd one, for that very reason. But if you boot
with upstart (Ubuntu's default still), cgmanager creates cgroups.
cgmanager puts tasks into
