From owner-freebsd-questions@FreeBSD.ORG Thu Feb 19 18:58:56 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3115F74A for ; Thu, 19 Feb 2015 18:58:56 +0000 (UTC) Received: from mail.tridentusa.com (mail.tridentusa.com [96.225.19.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mail.tridentusa.com", Issuer "mail.tridentusa.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C1B3AB1 for ; Thu, 19 Feb 2015 18:58:54 +0000 (UTC) Received: (qmail 97417 invoked from network); 19 Feb 2015 13:52:12 -0500 Received: from john-j (HELO ?172.16.0.90?) (jjohnstone@tridentusa.com@172.16.0.90) by mail.tridentusa.com with SMTP; 19 Feb 2015 13:52:12 -0500 Message-ID: <54E630CA.3020909@tridentusa.com> Date: Thu, 19 Feb 2015 13:51:54 -0500 From: John Johnstone User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: Syslogd: remote logging saves to wrong file References: <20150214155552.3216c695@rsbsd.rsb> In-Reply-To: <20150214155552.3216c695@rsbsd.rsb> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Feb 2015 18:58:56 -0000 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.