Re: fsck progress not shown on boot with systemd as pid 1
On Sun, 27 Jul 2014, Michael Biebl wrote:
> Am 27.07.2014 00:26, schrieb Rick Thomas:
> > On Jul 25, 2014, at 12:33 PM, Michael Biebl <biebl@debian.org> wrote:
> >> So a future update of systemd will slightly change this behaviour:
> >> whenever there is a service that failed or takes longer then a certain
> >> threshold (iirc it's something like 5 secs), systemd will automatically
> >> switch into verbose mode
> >
> > Would it be possible to make the switch to verbose mode be “retroactive”
> > in the sense that it not only shows all messages from the moment of the
> > failure on — it also shows all the messages that lead up to the failure?
> >
> > This would require buffering up all messages, just in case there is a
> > failure and they need to be displayed, but IIUC this is being done
> > anyway.
>
> I think the answer to that is the journal.
>
> If you want to inspect everything from the beginning of the boot, you can
> just use journalctl -b. I think it would be quite confusing if systemd
> would suddenly display a whole bunch of messages which would all fly by
> immediately without a chance to read them.
Maybe so, but it is also confusing to have a blank screen with something
like this:
\|/-\|/... failed!
It would be really cool if it could display the all the messages [since boot
/ runlevel change (err... whatever systemd calls that)] from the service
that failed or which is taking too long to complete.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
Reply to: