-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-ID: <8fdca991-468c-4c16-5bee-eb13c6a98cda@Telcontar.valinor> On Wednesday, 2021-04-14 at 08:08 +0300, Andrei Borzenkov wrote:
On 13.04.2021 23:38, Carlos E. R. wrote:
On 13/04/2021 15.42, Per Jessen wrote:
Carlos E. R. wrote:
On 13/04/2021 15.14, Per Jessen wrote:
Peter Suetterlin wrote:
Per Jessen wrote: > > may be /var/log/boot.msg ?
No, nothing even remotely resembling 'boot' in there...
The boot.msg and boot.omsg files are handled/created by the klog.service. Standard part of systemd.
That's new.
Ignoring that I mistyped (wrote systemd instead of syslog), that klog service has been around for 7-8 years :-)
Yes, certainly. I was not saying that. But those two boot* files have been missing for some years here.
I noticed because I always uninstall plymouth; the files disappeared, and I was told (by Andrei Borzenkov perhaps?) that the boot log file was written by plymouth.
This is /var/log/boot.log, not "boot log". "boot log" is too ambiguous.
Intentionally :-) Not sure of the actual file name. cer@Telcontar:~> l /var/log/ | grep boot - -rw-r--r-- 1 root root 16675 Jun 10 2013 boot.log - -rw-r--r-- 1 root root 97668 Apr 11 11:40 boot.msg - -rw-r--r-- 1 root root 97709 Apr 10 22:19 boot.omsg cer@Telcontar:~>
I don't know what writes them now, but it is not plymouth as I don't have it.
If "them" refers to /var/log/boot.(o)msg - service klog.service which is part of syslog-service.
Yes, I know that now. - -- Cheers, Carlos E. R. (from openSUSE 15.2 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYHbVaxwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVTJkAn3/4mFe0MPl3T9FqQ6hY dKy1ZuruAKCMRuRviVodnM/GrvdDZh8sv14T2g== =zjw0 -----END PGP SIGNATURE-----