Date: Thu, 19 Feb 2015 13:51:54 -0500 From: John Johnstone <jjohnstone@tridentusa.com> To: freebsd-questions@freebsd.org Subject: Re: Syslogd: remote logging saves to wrong file Message-ID: <54E630CA.3020909@tridentusa.com> In-Reply-To: <20150214155552.3216c695@rsbsd.rsb> References: <20150214155552.3216c695@rsbsd.rsb>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2/14/2015 8:55 AM, Beeblebrox wrote: > I'm trying once more to get remote logging to work properly. The > handbook states > (https://www.freebsd.org/doc/handbook/configtuning-syslog.html): > > "On the log server, edit /etc/syslog.conf to specify > +192.168.2.n/24 > *.* /var/log/client1.log" > > This does not work however, and all client logs are being saved to > host's own /var/log/messages instead of the per client logfile > specified in syslog.conf. > > Host syslogd is started with the (-a) flag, so there's no problem with > listening. I used the syntax described in the handbook such as: +logclient.example.com *.* /var/log/logclient.log followed by -logclient.example.com I had to include `-logclient.example.com' to exclude the logclient messages from the host's messages file. These lines had to be placed in syslog.conf ahead of the rest of the specifications there. My logclient logging did go in logclient.log though. It is strange that the client messages are obvious being seen since they're being put in the host's messages file. Per the handbook I used the -d and -v syslogd options when I was working on this. - John J.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54E630CA.3020909>