[systemd-devel] Allow stop jobs to be killed during shutdown
Andrey Borzenkov
arvidjaar at gmail.com
Fri Jan 24 10:32:40 PST 2014
В Fri, 24 Jan 2014 18:46:06 +0100
Lennart Poettering <lennart at poettering.net> пишет:
> 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
User systemd does not attempt to exit because it does not see signal
(RTMIN+24). I'm ready to try to debug it further but simply do not know
where - epoll handling by systemd is black magic to me.
> then if you figured out which of the two cases, you'd have to figure out
> why that is...
>
> Lennart
>
More information about the systemd-devel
mailing list