Reputation
2,088
Top tag
Next privilege 2,500 Rep.
Create tag synonyms
Badges
3 19 33
Impact
~100k people reached

Feb
21
revised How to pause (or capture) the messages that fly by at the end of startup sequence?
added 1996 characters in body
Feb
21
comment How to pause (or capture) the messages that fly by at the end of startup sequence?
@don_crissti: I don't understand how the output of journalctl -b [-a] can come even close to resembling the diagnostic messages I see at the end of startup. Even in the numbers of lines, the two sets of information differ by a couple orders of magnitude (I see a couple dozen lines' worth of messages at the end of startup, they don't even fill my screen, whereas the output of journalctl -b [-a] shows > 2200 lines). I must conclude that our systems are configured radically differently.
Feb
21
comment How to pause (or capture) the messages that fly by at the end of startup sequence?
@JonCarter: I've added an EDIT3 to my post to answer one of your questions. The short version is: Debian 8.3/jessie.
Feb
21
revised How to pause (or capture) the messages that fly by at the end of startup sequence?
added 325 characters in body
Feb
21
revised How to pause (or capture) the messages that fly by at the end of startup sequence?
added 95 characters in body
Feb
21
revised How to pause (or capture) the messages that fly by at the end of startup sequence?
added 2 characters in body
Feb
21
revised How to pause (or capture) the messages that fly by at the end of startup sequence?
added 2 characters in body
Feb
21
comment How to pause (or capture) the messages that fly by at the end of startup sequence?
@meuh: that looks like the right direction, but I have not gotten it to work yet. I added the lines you mentioned to /etc/rsyslog.conf, and rebooted, but the /var/log/boot.log file was not created. I then created the file (touch /var/log/boot.log), plus chgrp adm'd and chown 640'd it (to match the ownership/permissions of the other log files under /var/log), and rebooted. The /var/log/boot.log file remained empty. I searched the logs for any error relating to my modification of /etc/rsyslog.conf, but did not find anything. I have not yet found any documentation on this.
Feb
21
comment How to pause (or capture) the messages that fly by at the end of startup sequence?
@meuh: there's no /var/log/boot.log in my system. There's a /var/log/boot file, but its modification time is Feb 13 13:39. Since I've rebooted my system multiple times since then, and seen all those diagnostic messages at every one of those reboots, this file can't possibly contain what I'm looking for. There's also a file /var/log/bootstrap.log, but it's empty.
Feb
21
revised How to pause (or capture) the messages that fly by at the end of startup sequence?
added 257 characters in body
Feb
21
comment How to pause (or capture) the messages that fly by at the end of startup sequence?
@don_crissti: with any of the versions of journalctl you mentioned, if I pipe the output through grep OK I get zero hits, even though I see tons of OK's flashing right before the login prompt. This proves to me, beyond any doubt, that whatever it is that these commands print out, it is most definitely not what I am looking for.
Feb
21
comment How to pause (or capture) the messages that fly by at the end of startup sequence?
@Theophrastus: I'm beginning to see why so many Linux users detest systemd, and I'm about to join their ranks myself... I have edited my fn 4 to spell out (even more) why journalctl --boot | grep -i fail, for example, is not what I'm looking for.
Feb
21
revised How to pause (or capture) the messages that fly by at the end of startup sequence?
added 371 characters in body
Feb
21
comment How to pause (or capture) the messages that fly by at the end of startup sequence?
@don_crissti: no, that's what I took pains to explain in fn 4: it is possible that the output of journalctl -b contains information that, to the expert, would be for all intents and purposes equivalent to what is conveyed by the startup messages, but it does not contain those messages verbatim. I'll edit my post to make this more explicit.
Feb
21
asked How to pause (or capture) the messages that fly by at the end of startup sequence?
Feb
18
accepted On the relationship between shell initialization and desktop apps after a “graphic login”
Feb
18
accepted On `fork`, children processes, and “subshells”
Feb
18
revised On `fork`, children processes, and “subshells”
edited body
Feb
18
asked On `fork`, children processes, and “subshells”
Feb
18
asked On the relationship between shell initialization and desktop apps after a “graphic login”