[systemd-devel] Allow stop jobs to be killed during shutdown

[Ivan Shapovalov]

On Friday 24 January 2014 at 18:46:06, Lennart wrote:
> On Fri, 24.01.14 21:10, Ivan Shapovalov (intelfx100 at gmail.com) wrote:
> > > > > However, something like that can never be the default, we need to
> > > > > give
> > > > > services the chance to shut down cleanly and in the right order
> > > > 
> > > > then bugs like https://bugzilla.redhat.com/show_bug.cgi?id=1023820
> > > 
> > > I have so far never encountered this issue, but I fear this is a bug
> > > where somebody who can reproduce this needs to sit down and debug a
> > > bit...
> > > 
> > > Lennart
> > 
> > Any advices on how to do that?
> > I have both the issue (reproducible on each shutdown) and will to debug.
> 
> Well, enable the debug shell, and then from there try to figure out why
> things are stuck. i.e. whether it is systemd --user that really never
> exits. Or whether it actually exits but PID 1 doesn't notice it. And
> then if you figured out which of the two cases, you'd have to figure out
> why that is...
> 
> Lennart

So, in my case it apparently was due to PEBKAC. The user instance, which I 
(ab)use for running some desktop services, receives "start exit.target", then 
stops all running services and at some point something enqueues "isolate 
default.target", which happily outweighs exit.target. As a result, service 
shutdown never finishes and the user instance never exits.

Now I've fixed this (in my own scripts) and the user instance seems to exit 
normally. The distro is Arch, for the record.

-- 
Ivan Shapovalov / intelfx /
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 230 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20140125/629be03c/attachment-0001.pgp>