uhm the below is the result of people using "reply-all" on lists and the other side filters out duplicates caused by leading the off-list reply survives if it was faster
-------- Original-Nachricht -------- Betreff: Re: [systemd-devel] Allow stop jobs to be killed during shutdown Datum: Fri, 24 Jan 2014 18:59:56 +0100 Von: Reindl Harald <h.rei...@thelounge.net> An: Lennart Poettering <lenn...@poettering.net> Am 24.01.2014 18:53, schrieb Lennart Poettering: > On Fri, 24.01.14 18:45, Reindl Harald (h.rei...@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 ???? the timeout is "TimeoutStopSec" or "TimeoutStopSec" > Oh, and where I wrote "eye of sauron" I meant "cylon" irrelevant - whatever it is it says "waiting for service xyz" but it does *not* say how long it waits until it will give up the interesting value is "TimeoutStopSec-TimeWaiting"
signature.asc
Description: OpenPGP digital signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel