Syslogd: remote logging saves to wrong file

John Johnstone jjohnstone at
Thu Feb 19 18:58:56 UTC 2015

On 2/14/2015 8:55 AM, Beeblebrox wrote:
> I'm trying once more to get remote logging to work properly. The
> handbook states
> (
> "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:
*.*     /var/log/logclient.log

followed by

I had to include `' 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.

More information about the freebsd-questions mailing list