Date: Mon, 7 Aug 2000 11:23:05 +0100 From: David Malone <dwmalone@maths.tcd.ie> To: Gregory Bond <gnb@itga.com.au> Cc: stable@freebsd.org Subject: Re: logging kern.info to remote machine Message-ID: <20000807112305.A26510@walton.maths.tcd.ie> In-Reply-To: <200008070808.SAA03793@lightning.itga.com.au>; from gnb@itga.com.au on Mon, Aug 07, 2000 at 06:08:45PM %2B1000 References: <200008070808.SAA03793@lightning.itga.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 07, 2000 at 06:08:45PM +1000, Gregory Bond wrote: > Running "syslog -d" on both machines, and then "logger -p kern.info test" on > the source machine, we see the packet is received by syslogd on the loghost, > But it is never logged anywhere. This is despite the line in syslog.conf that > says > *.notice;kern.debug;lpr.info;mail.crit;news.err /var/log/messages > > However a message at kern.err _is_ properly logged on the loghost by this rule > (presumably because it is trapped by the "*.notice" clause). > > Any clues? I note that if syslogd reads a message which claims to be a kernel message from anything other than the kernel, it replaces the facility with user.whatever. You're probably running into this. Maybe this should be listed in the syslogd or syslog.conf man page? David. 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?20000807112305.A26510>