[systemd-devel] Allow stop jobs to be killed during shutdown
Andrey Borzenkov
arvidjaar at gmail.com
Mon Jan 27 07:05:04 PST 2014
В Mon, 27 Jan 2014 15:29:15 +0100
Lennart Poettering <lennart at poettering.net> пишет:
> On Mon, 27.01.14 13:42, Tom Gundersen (teg at jklm.no) wrote:
>
> > > So maybe something like this: In addition to the boolean values for
> > > systemd.show_status= on the kernel cmdline (or ShowStatus= in
> > > system.conf), we'd add a third value called "auto". If that is set
> > > we'd boot up without any status output, until either at least one
> > > service failed, or at least one job reaches its timeout half-way.
> >
> > For people like me who has an attention span of about five seconds,
> > half-way to the timeout is still a really long time to just sit there.
> > Maybe just use the same timeout as the eye-of-cylon thingie?
>
> Yeah, maybe. Figuring out good timeouts its probably something one
> should do when actually playing around with it and checking how things
> "feel" if this is implemented...
>
> > > When
> > > that point is reached we'c continue the entire rest of the boot with
> > > status output enabled.
> >
> > Hm, maybe only do this if something actually failed/reached the
> > timeout, and not if we just show the eye-of-cylon for a while and then
> > continue normally?
>
> Hmm, possibly, yeah, but we probably should explain that
> too... i.e. "Turning off boot-time status output again, since timeout is
> resolved" or so... But maybe this ultimately gets too confusing...
>
> Note that this all is just an issue on non-Plymouth systems. If you use
> Plymouth then things are much nicer anyway, since the output is always
> generated, just not visible on screen until the user hits Esc.
>
Yes, but you still want to virtually press ESC to attract user
attention to a problem ...
More information about the systemd-devel
mailing list