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

Lennart Poettering lennart at poettering.net
Fri Jan 24 07:15:04 PST 2014


On Fri, 24.01.14 16:09, Reindl Harald (h.reindl at thelounge.net) wrote:

> Am 24.01.2014 16:03, schrieb Lennart Poettering:
> > It is our job to shutdown all services cleanly. A number of services
> > needs this, since they need to bring their files into a safe state
> > before quitting, and mark them as "offline". We cannot just drop that.
> > 
> > Note however, that we add have timeouts on all service shutdown
> > commands, so when some service hangs it will be forcibly aborted with
> > SIGKILL after 90s.
> > 
> > That all said, you can just shutdown with "systemctl poweroff -f"
> > instead of normal "systemctl poweroff". This will still bring the file
> > systems in order and things, but wil not bother with shutting down
> > system services cleanly, but simply SIGTERM and SIGKILL them after a
> > much shorter timeout.
> > 
> > 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

-- 
Lennart Poettering, Red Hat


More information about the systemd-devel mailing list