Date: Wed, 14 Feb 2001 18:44:28 -0500 From: Brian Reichert <reichert@numachi.com> To: Mark Hartley <freebsd@drapple.com> Cc: freebsd-security@freebsd.org Subject: Re: Syslogd stops working Message-ID: <20010214184428.U91352@numachi.com> In-Reply-To: <20010214154342.A48740@router.drapple.com>; from freebsd@drapple.com on Wed, Feb 14, 2001 at 03:43:43PM -0800 References: <20010214154342.A48740@router.drapple.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 14, 2001 at 03:43:43PM -0800, Mark Hartley wrote: > 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? I've had issues with syslog logging to a serial console. It that you are doing? > > > Mark. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-security" in the body of the message > -- Brian 'you Bastard' Reichert <reichert@numachi.com> 37 Crystal Ave. #303 Daytime number: (603) 434-6842 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010214184428.U91352>