From owner-freebsd-security  Wed Feb 14 15:41:26 2001
Delivered-To: freebsd-security@freebsd.org
Received: from router.drapple.com (c1024475-b.salem1.or.home.com [24.10.78.207])
	by hub.freebsd.org (Postfix) with ESMTP id 558FC37B401
	for <freebsd-security@freebsd.org>; Wed, 14 Feb 2001 15:41:24 -0800 (PST)
Received: (from mark@localhost)
	by router.drapple.com (8.9.3/8.9.3) id PAA48752
	for freebsd-security@freebsd.org; Wed, 14 Feb 2001 15:43:43 -0800 (PST)
	(envelope-from mark)
Date: Wed, 14 Feb 2001 15:43:43 -0800
From: Mark Hartley <freebsd@drapple.com>
To: freebsd-security@freebsd.org
Subject: Syslogd stops working
Message-ID: <20010214154342.A48740@router.drapple.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

I have several different FreeBSD servers which I've upgraded recently
through cvsup and rebuilding world due to the bind, ipfw, and ssh holes.

However, I have one machine which I cvsupped and rebuilt on Jan 29th
which has stopped logging to syslog.  I've checked my syslog.conf file
and everything seems fine.  I had just been noticing a lack of people
"banging" on my firewall.  I got to looking, and syslog has not been
functioning since that point.  This is a very serious issue for me
as I've potentially missed several important syslog notices.  I checked,
and syslogd is in fact running.

Any ideas why this is happening and what I can do to remedy it?


Mark.


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