Hi,
I didn't turn anything off in journald.conf, it is all the default
settings. I do get every boot log just fine for example within
emergency.target, also tried with multi-user.target just for the sake of
trying. I could pastebin them somewhere or at least try to if you want
to have a look, but I didn't find anything suspicious in journalctl or
dmesg.
Thanks
Lennart Poettering a écrit :
On Mo, 29.04.19 11:06, Ellis (contact@xxxxxxxxx) wrote:
Hi,
after some manual testing on my end, I can confirm two things:
1. systemd really takes care of /run as it should
and 2. I still have no log prior to 'received sigterm from PID 1' when the
real root is booted up.
I intentionally messed up my kernel cmdline giving it a wrong rootfs
partition, was dropped into emergency mode, created a directory named
testing in /run, mounted the right filesystem for /sysroot, typed exit,
booted up to real root, /run/testing is still there.
However I noticed that /run/log was empty, both in the initrd and in the
real root.
So, I'm even more confused.
if you acquire a shell in the initrd, and type "journalctl", what do
you get?
have you turned off storing of logs with Storage=no or so?
anything in dmesg?
Lennart
--
Lennart Poettering, Berlin
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
