From owner-freebsd-security Wed Feb 14 15:54:38 2001 Delivered-To: freebsd-security@freebsd.org Received: from sonar.noops.org (adsl-63-195-97-84.dsl.snfc21.pacbell.net [63.195.97.84]) by hub.freebsd.org (Postfix) with ESMTP id B50AC37B401 for ; Wed, 14 Feb 2001 15:54:35 -0800 (PST) Received: from localhost (root@localhost) by sonar.noops.org (8.9.3/8.9.3) with ESMTP id PAA02640; Wed, 14 Feb 2001 15:54:18 -0800 (PST) (envelope-from root@noops.org) Date: Wed, 14 Feb 2001 15:54:18 -0800 (PST) From: Thomas Cannon To: Mark Hartley Cc: freebsd-security@FreeBSD.ORG Subject: Re: Syslogd stops working In-Reply-To: <20010214154342.A48740@router.drapple.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Are you 100% positively certain that there are no spaces in your syslogd.conf file, and that everything in there is tab delimited? -tcannon > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message