Date: Wed, 20 Feb 2002 10:44:10 +0800 From: francisv@dagupan.com To: freebsd-stable@FreeBSD.ORG Subject: RE: strange behavior of syslogd: bug or operator failure? Message-ID: <10F29E27A956D511B0940050DA8D86A9340F7F@apmail.dagupan.com>
next in thread | raw e-mail | index | archive | help
One more question: did you use mergemaster or something similar to update
your /etc/syslog.conf file?
-----Original Message-----
From: Crist J. Clark [mailto:cjc@FreeBSD.ORG]
Sent: Wednesday, February 20, 2002 10:35 AM
To: JJ Behrens
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: strange behavior of syslogd: bug or operator failure?
On Tue, Feb 19, 2002 at 05:53:56PM -0800, JJ Behrens wrote:
> > > After upgrading to 4.5-stable syslogd stops logging messages from
> > > our ciscos. After investigating into problem it seems that syslogd
> > > have no ideas about file it need to save messages: some of them logged
> > > onto console (in fact into /var/log/console), others - into
> > > /var/log/messages. One difference - messages originated from different
> > > hosts.
> > > Is something wrong with syslogd? It works before upgrade.
> >
> > Do /var/log/{a,b,c,xxx} exist?
>
> Hmm, it seems like they removed syslog from /etc/services, or at least
that's
> an error message that I get when I boot. I don't see anything about this
on
> the PR list. I suspect these two things are related.
Who is "they?" It most definately is in a stock FreeBSD services(5)
file.
--
Crist J. Clark | cjclark@alum.mit.edu
| cjclark@jhu.edu
http://people.freebsd.org/~cjc/ | cjc@freebsd.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?10F29E27A956D511B0940050DA8D86A9340F7F>