Is there a reasonable procedure for a system administrator to view all the fsck
messages?
On my current Fedora 29 system, I can view all the fsck
messages from my current boot like this:
sudo journalctl -b /usr/lib/systemd/systemd-fsck
However, it is a hack that assumes fsck
writes messages to stdout
/ stderr
. It does not allow for a hypothetical fsck
which detects that it is run from systemd, and sends log messages through the syslog or journald socket e.g. in order to set appropriate "priority" for each message.
Is there a cleaner method, that works even if some fsck
sends its log messages directly to journald?