Date: Wed, 20 Sep 2023 21:59:08 +0200 From: Ede Wolf <listac@nebelschwaden.de> To: Freebsd-questions@freebsd.org Subject: Re: Capturing Boot Messages? Message-ID: <24e16c1d-520d-47eb-912c-923514d8a4ed@nebelschwaden.de> In-Reply-To: <48DF5481-1F7C-4BF6-89D8-F19388449423@prime.gushi.org> References: <26de1d95-abff-465d-b25c-1b2465e80342@nebelschwaden.de> <48DF5481-1F7C-4BF6-89D8-F19388449423@prime.gushi.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 20.09.23 um 20:40 schrieb Dan Mahoney: > > >> On Sep 20, 2023, at 10:53 AM, Ede Wolf <listac@nebelschwaden.de> wrote: >> >> Hello, >> >> I am seeing boot messages on screen, errors from rc.conf, that I have yet to find in any log. Neither dmesg, nor /var/run/dmesg.boot nor in /var/log/messages. >> >> Any chance to reread the full boot process somewhere or to set up full boot logging? > > So anything that came from the kernel before init started would get stuck into /var/run/dmesg.boot… > > Anything that came from init, and the rc subsystem, you could enable using the hints in /etc/syslog.conf > > # uncomment this to log all writes to /dev/console to /var/log/console.log > # touch /var/log/console.log and chmod it to mode 600 before it will work > #console.info /var/log/console.log > > Noting from a run of rcorder /etc/rc.d/* that there are some things that start before syslogd, so it might not catch those. > > -Dan Thanks, that is another good way, in addition to dmesg -a, that also solved my issue. As this is generally a very useful thing to do, I've enabled it. It does shows the error messages I have been looking for, as they came up quite late in the boot process.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?24e16c1d-520d-47eb-912c-923514d8a4ed>