Date: Mon, 13 Sep 1999 00:11:28 -0500 From: John Lengeling <johnl@raccoon.com> To: betterformat <betterformat@astea.com.au> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: syslog problem Message-ID: <37DC8780.E84ACF26@raccoon.com> References: <199909100734.RAA09757@astea.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
For some reason, I too have always had problems making changes to the syslog.conf file. I use the following tools to help debug syslog.conf changes: 1. Put syslogd in debug mode. 2. Use logger(1) command to send test messages to syslogd. 3. Run ktrace(1) on the syslogd process and see if it is getting the log requests and also to see if it had problems opening the log files. 4. Run tcpdump(1) to watch the network for syslog requests. johnl betterformat wrote: > > Hi All, > I had my fbsd firewall logging to the console but I wanted > to log to a file instead for a while..... so I made the following > changes:- > > *.* @10.0.0.15 > *.* /dev/console > > was changed to:- > > *.* @10.0.0.15 > *.* /var/log/sys.log > > It stopped logging to the console (I expected this) and didn't > start logging to the specified location (yes the location does > exist). So I switched back to the original config and now it > doesn't even log to the console..... I didn't edit anything else. > > Does anyone have any ideas as to what I might have broken? > > Thanks in advance, > Leo > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?37DC8780.E84ACF26>