On 04/16/2013 07:45 PM, Kevin Wilson wrote:
No I moved /usr/lib/systemd/systemd-cgroups-agent to some backup.
and made sure that:
ls /usr/lib/systemd/systemd-cgroups-agent
ls: cannot access /usr/lib/systemd/systemd-cgroups-agent: No such file
or directory
Now I tried killing two services that I know are under systemd cgroups:
cat /sys/fs/cgroup/systemd/system/bluetooth.service/tasks
671
Apr 16 20:40:05 localhost systemd[1]: bluetooth.service: main process
exited, code=killed, status=9/KILL
Apr 16 20:40:05 localhost systemd[1]: Unit bluetooth.service entered
failed state
And with mcelog it was the same:
...
Apr 16 20:33:46 localhost systemd[1]: mcelog.service: main process
exited, code=killed, status=9/KILL
Apr 16 20:33:46 localhost systemd[1]: Unit mcelog.service entered failed state
...
both folders, bluetooth.service and mcelog.service (under
/sys/fs/cgroup/systemd/system/) were removed.
How come ? could it be that the messages to the DBus are not sent
by systemd-cgroups-agent?
In these two cases it was sufficient for systemd to receive the SIGCHLD
signal to detect the death of the service. But this won't work for every
service.
Michal
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
