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

[Bernhard Übelacker]

Am 30.09.2014 17:54, schrieb Michael Biebl:
>> 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?

Hello Michael,
thanks for your very fast response.

Then the first point about the timeout is completely resolved.


The second point probably applies only to user sessions because there
the user can start multiple programs, as many as he wants.

The user probably will close also all X windows but there are some
processes in the background left.
Then systemd sends them a SIGTERM and they should end themself immediately.
If they do not end then they cause this delay and the user has no clue
which process it was.

Systemd knows exactly for which process we are waiting and could
probably show the process information.

Probably therefore it is still a valid whishlist point for v215.
Will try with a test system.

Thanks for all your work.

Kind regards,
Bernhard