On 2015-10-09 15:13, Lucas, Sascha wrote:
> Somewhat strange is, that in debian systemd puts it in the user name
> hierarchy. @Georg: my it be possible that ganeti-noded is started from
> a shell initiated by the user with ID 1000? Situations where this may
> happen are possibly "cluster init" or "node add". So that ganeti-noded
> inherits the cgroup hierarchy from its parent process?
- At first I initiated the cluster via: ssh as user && sudo -i &&
gnt-cluster init [...]
- Still, the uid (should have?) changed because of sudo -i
- After this I rebooted, the result was the just posted extract of
/proc/1728/cgroup, especially
1:name=systemd:/user.slice/user-1000.slice/session-2.scope
- ganeti(-noded) was started automatically via systemd.
- (Not sure at this point, why it's (still) associated with the user?)
- Second run, which I just did now: ssh as root && gnt-cluster init
[...] && reboot, results in:
# cat /proc/$(pidof -x ganeti-noded)/cgroup
9:perf_event:/
8:net_cls,net_prio:/
7:freezer:/
6:devices:/
5:memory:/
4:blkio:/
3:cpu,cpuacct:/
2:cpuset:/
1:name=systemd:/system.slice/ganeti.service
> I wonder if you restart Ganeti via systemctl if the name hierarchy
> would change to "/system.slice/ganeti.service"?
You're some somewhat right..still I don't understand, why this isn't
happening via the first way.
But, as I wrote, I've got no clue (yet) about systemd and cgroup
internals.