Bug#763510: systemd: A stop job is running for Session. Show user an timeout and the blocking process.

[Michael Biebl]

Am 30.09.2014 um 17:28 schrieb Bernhard Übelacker:
> Package: systemd
> Version: 208-8
> Severity: wishlist
> Tags: upstream patch
> 
> Dear Maintainer,
> lately I noticed that reboots or shutdowns are waiting for
> 90 seconds with the following message:
>> [  *** ] A stop job is running for Session 1 of user bernhard
> 
> (Indeed the user will see this message only if the "quiet"
> kernel parameter is omitted.)

Not anymore with v215. If a unit hits a timeout or a failure, systemd
will switch into verbose automatically. [1]

> This delay is produced by an process which is not responding
> to SIGTERM. (In my case kdesud.)
> 
> But to the user it is neither shown how long systemd is waiting
> until signal SIGKILL is sent or which process caused this delay.

This is also fixed in v215. systemd will show how long the timeout is
and how much time has already passed.

See attached screenshot.

I think this should address your points sufficiently and this bug can be
closed, right?

Michael




[1]
http://www.freedesktop.org/software/systemd/man/systemd.html#systemd.show_status=


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: screenshot.png
Type: image/png
Size: 14108 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20140930/47a4ffcb/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20140930/47a4ffcb/attachment-0002.sig>