But it should be persisted by default in /var/log, so there should be a
unit somewhere that if the log has information then it appends it in a
file and gets logrotated.
That way, if a server or PC is acting strange, one could look there to
see if something strange happened to the filesystem and wh
Thank you for the clarification Martin.
I was able to confirm that the fsck results are located in
/run/initramfs/fsck.log on my test system as you described.
I found that if the /etc/default/grub file was modified to include:
GRUB_CMDLINE_LINUX="fsck.mode=force"
Then after running "sudo update
This is unrelated to systemd. Instead, fsck'ing the root file system got
moved into the initrd. You can find the log in /run/initramfs/fsck.log.
** Package changed: systemd (Ubuntu) => initramfs-tools (Ubuntu)
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed => Invalid
--
You re
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.n
Added milestone xenial-updates
** Changed in: systemd (Ubuntu)
Milestone: None => xenial-updates
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1619753
Title:
systemd
5 matches
Mail list logo
