On Thu, 15.01.15 09:39, Colin Guthrie (gm...@colin.guthr.ie) wrote: > Ross Lagerwall wrote on 14/01/15 22:41: > > On Mon, Jan 12, 2015 at 09:04:35PM +0300, Andrei Borzenkov wrote: > >> В Mon, 12 Jan 2015 10:34:07 +0000 > >> Colin Guthrie <co...@mageia.org> пишет: > >> > >>> > >>> Anyway, assuming the process is in the .mount unit cgroup, should > >>> systemd detect the umount and kill the processes accordingly, and if > >> > >> It does not do it currently. It only starts killing if (u)mount times > >> out. Otherwise if umount is successful it goes to stopped state > >> immediately. Although it probably should, even for the sake of user > >> space helpers. > >> > >>> not, should calling "systemctl status" on .mount units show processes > >>> even if it's in an inactive state? > >>> > >> > >> I believe something very similar (not only for mount units) was > >> reported recently, but I do not have reference handy. I mean, processes > >> belonging to stopped unit (e.g. with KillMode=none) are not displayed. > >> > > > > This commit is probably needed: > > > > http://cgit.freedesktop.org/systemd/systemd/commit/?id=dab5bf859900c0abdbf78c584e4aed42a19768cd > > That indeed looks like a likely candidate. I'll try breaking things > again and checking status output with this patch applied.
Did this fix things for you? Are all processes invoked by the mount unit terminated cleanly now on umount? Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
