Date: Wed, 1 Nov 2006 10:29:00 -0800 From: John-Mark Gurney <gurney_j@resnet.uoregon.edu> To: "Rick C. Petty" <rick-freebsd@kiwi-computer.com> Cc: freebsd-geom@freebsd.org Subject: Re: burnt again by gmirror Message-ID: <20061101182859.GH25511@funkthat.com> In-Reply-To: <20061031215241.GA57997@keira.kiwi-computer.com> References: <20061031195442.GA55478@keira.kiwi-computer.com> <4547AD9B.5050503@centtech.com> <20061031204659.GA56766@keira.kiwi-computer.com> <20061031205857.GA15861@garage.freebsd.pl> <20061031215241.GA57997@keira.kiwi-computer.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Rick C. Petty wrote this message on Tue, Oct 31, 2006 at 15:52 -0600:
> I wish either fsck was less noisy or that the kernel would take a
> snapshot of the msgbuf right before starting init, so only the kernel
> messages would get copied into /var/run/ when the rc scripts do their
> thing...
This is a bug IMO that console messages get added to the dmesg buffer..
This was changed in 4.3. dmesg sees what messages are console
messages and skips over them. If you provide the -a option to dmesg,
you get what was dumped to the console:
-a Show all data in the message buffer. This includes any syslog
records and /dev/console output.
W/o this bug/feature, we'd never have to worry about /dev/console
messages overflowing the kernel messages, which is a lot more common
than kernel messages overflowing before rc scripts run and hit saving
dmesg.
In 6.2 and HEAD, I've doubled the kernel message buffer to 64k for i386,
so it's less likely to overflow.
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061101182859.GH25511>