From owner-freebsd-questions@FreeBSD.ORG Mon Jun 5 19:23:44 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 660F216A90E for ; Mon, 5 Jun 2006 19:23:44 +0000 (UTC) (envelope-from nalists@scls.lib.wi.us) Received: from mail.scls.lib.wi.us (mail.scls.lib.wi.us [198.150.40.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0C5843D46 for ; Mon, 5 Jun 2006 19:23:43 +0000 (GMT) (envelope-from nalists@scls.lib.wi.us) Received: from [172.26.2.238] ([172.26.2.238]) by mail.scls.lib.wi.us (8.13.1/8.13.1) with ESMTP id k55JNfLl011047; Mon, 5 Jun 2006 14:23:41 -0500 (CDT) (envelope-from nalists@scls.lib.wi.us) Message-ID: <448484BD.8090408@scls.lib.wi.us> Date: Mon, 05 Jun 2006 14:23:41 -0500 From: Greg Barniskis User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <44843B61.5050209@chrismaness.com> <448469D5.8060700@scls.lib.wi.us> <20060605105358.Q54670@ns1.internetinsite.com> <44847336.9050908@scls.lib.wi.us> <448xobpi30.fsf@be-well.ilk.org> In-Reply-To: <448xobpi30.fsf@be-well.ilk.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Chris Maness Subject: Re: dmesg not working on new system X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jun 2006 19:23:46 -0000 Lowell Gilbert wrote: > Greg Barniskis writes: > >> Chris Maness wrote: >>> >>> On Mon, 5 Jun 2006, Greg Barniskis wrote: >>> >>>> Chris Maness wrote: >>>>> I just installed 6.1 and upgraded to RELEASE-p1. The command >>>>> dmesg is not displaying any kernel messages, any suggestions? >>>> Suggests all is well? >>>> >>>> dmesg outputs stuff from the current system message buffer, which >>>> contains your boot messages right after booting but those can get >>>> flushed over time. Boot messages are saved to a file though, for >>>> reference. >>>> >>>> more /var/run/dmesg.boot >>>> >>> I just thought it was strange because every other system I have it >>> at least displays dmesg.boot if there is no other messages. Is this >>> new behavior for 6.1? >> Not new behavior. A dmesg on any of my running systems (4.x, 5.x) >> returns nothing after a time. You were just catching it before the >> buffer was flushed. I don't know what triggers that, and it is >> possible that the trigger/timing of it may have changed in 6.x (and as >> always, YMMV). > > Interesting. Does "dmesg -a" show anything different? > > Sure. On a mail server, -a reveals tons of SMTP timed out messages (primarily spammers who cut and run when 550'd). On a firewall, -a shows tons of ipfw log messages. On a web server, -a shows mainly ssh login (and su) success/failure. Chris Howells wrote: > dmesg is not flushed here. Hmmm.... interesting. It has always eventually flushed around here, which prompted me to read the dmesg man page, which pointed me at /var/run/dmesg.boot. I never really thought about it much after that, and really still don't think it too odd... but if anyone thinks the behavior is erratic and in need of troubleshooting, I'll try to answer any other questions about my setup. But I don't see anywhere that the man page says "dmesg will always report the boot messages no matter what". It says it reads the system message buffer, and when something is a buffer I immediately think of it as a temporary thing. YMMV, obviously. -- Greg Barniskis, Computer Systems Integrator South Central Library System (SCLS) Library Interchange Network (LINK) , (608) 266-6348