Date: Wed, 27 Apr 2005 20:53:57 +0200 From: Marc Santhoff <M.Santhoff@t-online.de> To: "FreeBSD stable (Liste)" <freebsd-stable@freebsd.org> Subject: Re: [4.11] sysctl reports garbage Message-ID: <1114628037.292.3.camel@zaphod.das.netz> In-Reply-To: <20050427183147.GC6256@stack.nl> References: <1114623987.302.82.camel@zaphod.das.netz> <1114626276.302.89.camel@zaphod.das.netz> <20050427183147.GC6256@stack.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Am Mi, den 27.04.2005 schrieb Marc Olzheim um 20:31: > On Wed, Apr 27, 2005 at 08:24:36PM +0200, Marc Santhoff wrote: > > > That is 'kern.msgbuf' ;-) > > > > Hm, I've never seen such a verbose output before. > > > > Has anything changed in that area? And why does it still occur after a > > reboot, normally buffers are only temporarily valid(at least I thought > > so until a few minutes)? > > It's a fresh buffer every reboot. In you mail, it contained the last > part of your startup messages. > Everything that gets written to /dev/console is cycled through the > buffer and the last $(sysctl kern.consmsgbuf_size) KB is made accessible > via "sysctl kern.msgbuf". I still don't understand completly. In the file made like this: sysctl -a > garbage.txt there are the messages of at least three reboot cycles. The only explanation would be "dmesg" using this message buffer for it's output, that's what I used immediately before creating the text file. Marc
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1114628037.292.3.camel>