[Bug 1400394] Re: Unity8 fails to start applications under systemd init (cgmanager issue?)

[Martin Pitt]

We discussed that again via email. In summary:

 -  UAL and systemd units are non-overlapping use cases, and will not collide at all in practical use cases.
 - By itself, systemd only handles the "systemd" controller, which cgmanager should always stay out of
 - systemd units may configure cpu/memory/blkio cgroups with things like CPUShares=; so in principle, the started service could then do a cgmanager call to change these after the fact, but there's nothing stopping it from also doing these changes in /sys/fs/cgroup/ directly. This isn't a security feature, but a robustness/resource control one.

So what needs to happen:

 1. Ensure cgmanager doesn't change the "systemd" controller. (Should not happen in practice, but an explicit check can't hurt)
 2. Ensure cgmanager doesn't change an existing cgroup setup at startup, only upon request (which should already be true)
 3. Start cgmanager via socket/bus activation or at boot.


** Changed in: cgmanager (Ubuntu)
       Status: Won't Fix => Triaged

** Changed in: ubuntu-app-launch (Ubuntu)
       Status: New => Invalid

** Summary changed:

- Unity8 fails to start applications under systemd init (cgmanager issue?)
+ Unity8 fails to start applications, cgmanager is not started under systemd

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cgmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1400394

Title:
  Unity8 fails to start applications, cgmanager is not started under
  systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1400394/+subscriptions