Re: [systemd-devel] Scope units get SIGKILL when stopped, not SIGTERM

2014-11-30 Thread Michael Chapman
On Sun, 30 Nov 2014, Lennart Poettering wrote: The only solution that will really fix this for good is probably to move things to the new unified cgroup controller logic that finally gives us useful ways to get notifications for cgroups running empty. Also see what I just replied here: http://l

Re: [systemd-devel] Scope units get SIGKILL when stopped, not SIGTERM

2014-11-30 Thread Lennart Poettering
On Wed, 26.11.14 11:55, Michael Chapman (m...@very.puzzling.org) wrote: Heya, > When I stop a scope unit, it looks like all processes in it get a SIGKILL > immediately, not a SIGTERM. > > I believe this issue has been brought up before in > http://lists.freedesktop.org/archives/systemd-devel/201

[systemd-devel] Scope units get SIGKILL when stopped, not SIGTERM

2014-11-25 Thread Michael Chapman
Hello, When I stop a scope unit, it looks like all processes in it get a SIGKILL immediately, not a SIGTERM. I believe this issue has been brought up before in http://lists.freedesktop.org/archives/systemd-devel/2014-October/024452.html, but there was no resolution then. That thread indicate