[systemd-devel] [206] Randomly on shutdown, stop timeout for user at .service

Lennart Poettering lennart at poettering.net
Thu Jul 25 10:57:26 PDT 2013

On Wed, 24.07.13 14:50, Cristian Rodríguez (crrodriguez at opensuse.org) wrote:

> El 24/07/13 14:07, Gerardo Exequiel Pozzi escribió:
> >Hello
> >
> >I am using Arch Linux, and testing systemd-206 with linux-3.10.2 on
> >shutdown, sometimes randomly there is a long delay until user at 0.service
> >timeouts then systemd kills it.
> >
> I am seeing a similar behaviour here, but it hangs shutting down the
> session-1.scope unit.

So for this one I have an idea what happens. I figure inside that scope
unit you have a bash running? The bash ignores SIGTERM, and requires
SIGHUP instead for a clean termination. logind knew that and always sent
both. Since we moved everything to scope units it's now PID1's job to
kill the processes, and it doesn't explicitly send SIGHUP right now.

I figure we need to update the PID 1 scope kill logic to optionally send
both SIGTERM and SIGHUP to the cgroup members.


Lennart Poettering - Red Hat, Inc.

More information about the systemd-devel mailing list