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

[Colin Guthrie]

'Twas brillig, and Lennart Poettering at 24/01/14 17:53 did gyre and gimble:
> On Fri, 24.01.14 18:45, Reindl Harald (h.reindl at thelounge.net) 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.
>>>>>
>>>>> I didn't ask for any change to any default, I just asked for
>>>>> users to be able to make the shutdown process proceed when
>>>>> they have more information than systemd has about the chances
>>>>> of success of some random stop job.
>>>>>
>>>>> Without that, what you *will* get is people pulling the
>>>>> power plug which has a vastly greater chance of screwing up
>>>>> the system than not waiting for a single stop job.
>>>>
>>>> Perhaps just displaying the timeout would be useful here.
>>>
>>> We do that. Michal's "eye of sauron" animation is shown as soon as
>>> something blocks too long, and the name of the unit we are waiting for
>>> is shown.
>>
>> but there is nothing saying how long the timeout remains
>> "displaying the timeout" means a value in seconds
> 
> That delay is set to 5s.

What was meant here was that the *user* is not shown for how long the
"cylon" animation will play before systemd gives up and gets aggressive.

So there is a 5s timeout before displaying that, but all it does is tell
you how many jobs are waiting and not how long it's going to wait for them.

If the user sits and watches that animation for 20s they'll likely think
"ahh well this is stuck" and yank the cord, not knowing that things will
be done cleanly if they just wait another 10s.

If we displayed a timeout clock here too, users would be more willing to
wait.

Col


-- 

Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited http://www.tribalogic.net/
Open Source:
  Mageia Contributor http://www.mageia.org/
  PulseAudio Hacker http://www.pulseaudio.org/
  Trac Hacker http://trac.edgewall.org/