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

Kay Sievers kay at vrfy.org
Fri Jan 24 10:21:34 PST 2014


On Fri, Jan 24, 2014 at 6:53 PM, Lennart Poettering
<lennart at poettering.net> wrote:
> 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.
>
> (Oh, and where I wrote "eye of sauron" I meant "cylon". I guess this
> reveals my utter ignorance of all things science fiction and fantasy. We
> have this animation in there now since a while, and quite frankly, I
> have no idea where this supposedly is inspired from, except it's
> something with spaceships, which already turns me off so much I quickly
> stop listening...)

http://www.youtube.com/watch?v=oYZcZSVYx3M

Kay


More information about the systemd-devel mailing list