Date: Mon, 5 Apr 2004 06:05:52 +0100 From: Jez Hancock <jez.hancock@munk.nu> To: Rob <nospam@users.sourceforge.net> Cc: freebsd-questions@freebsd.org Subject: Re: dmesg bootup-info removed/overwritten by syslogd ? Message-ID: <20040405050552.GB21560@users.munk.nu> In-Reply-To: <4070DD61.9020102@users.sourceforge.net> References: <4070DD61.9020102@users.sourceforge.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 05, 2004 at 01:15:29PM +0900, Rob wrote: > I wanted to see my original bootup messages again. So I typed > dmesg, but all I got were 'arplookup' lines. > > I'm puzzled, where the bootup messages have gone? Overwritten by kernel debug messages. There have been a number of similar questions for a while, the gist is that when the dmesg buffer gets filled up, it starts to overwrite itself. This affects the daily periodic output and makes it look munged. I don't think any solution has ever been offered up - I'd certainly be interested in it :P > I have two files in /var/log: dmesg.today and dmesg.yesterday > Both files are completely filled with this line: > arplookup 147.46.50.254 failed: host is not on local network > > How can I see the original bootup messages from the kernel? One way is to cat the output from bootup dmesg into a file at boot time - in /etc/rc.local put this: dmesg > /var/log/dmesg.boot if you wanted to get fancy you could use the date(1) command to timestamp the files ala: dmesg > /var/log/dmesg.boot.`date "+%Y%m%d"` > Do I have to reboot for that :( ? Yup. Good luck. -- Jez Hancock - System Administrator / PHP Developer http://munk.nu/ http://jez.hancock-family.com/ - Another FreeBSD Diary http://ipfwstats.sf.net/ - ipfw peruser traffic logging
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040405050552.GB21560>