From owner-freebsd-stable  Mon Mar  5  6:30:16 2001
Delivered-To: freebsd-stable@freebsd.org
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by hub.freebsd.org (Postfix) with ESMTP id 955D937B718
	for <freebsd-stable@freebsd.org>; Mon,  5 Mar 2001 06:30:11 -0800 (PST)
	(envelope-from randy@psg.com)
Received: from randy by rip.psg.com with local (Exim 3.16 #1)
	id 14Zvzz-000LRx-00; Mon, 05 Mar 2001 06:30:07 -0800
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: David Malone <dwmalone@maths.tcd.ie>
Cc: FreeBSD Stable <freebsd-stable@freebsd.org>
Subject: Re: syslog overwriting dmesg?
References: <E14ZvIk-000KAE-00@rip.psg.com>
	<20010305142313.A91903@walton.maths.tcd.ie>
Message-Id: <E14Zvzz-000LRx-00@rip.psg.com>
Date: Mon, 05 Mar 2001 06:30:07 -0800
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>> i am seeing symptoms a lot like syslog overwriting dmesg and then
>> truncating it horribly.  it takes a few days, and is only happening on
>> one host.  is anybody else seeing anything like this?
> Have you tried "dmesg -a"? I believe the problem is known and that
> Robert Wattson is working on some changes which should help.

dmesg -a gives me a much bigger swath of syslog.  as this is the documented
behavior of -a, i did not whine about that.

but it's cheering that it is a known problem and robert is aware of it.  i
had this icy feeling in my stomach of a possible security issue.

randy

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message