From owner-freebsd-questions@FreeBSD.ORG Wed Mar 22 20:40:07 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6383716A449 for ; Wed, 22 Mar 2006 20:40:07 +0000 (UTC) (envelope-from bill@wiliweld.com) Received: from typhoon.he.net (typhoon.he.net [64.62.229.2]) by mx1.FreeBSD.org (Postfix) with SMTP id CF3F743D49 for ; Wed, 22 Mar 2006 20:40:06 +0000 (GMT) (envelope-from bill@wiliweld.com) Received: from liam.billschoolcraft.com ([63.204.157.14]) by typhoon.he.net for ; Wed, 22 Mar 2006 12:40:01 -0800 Date: Wed, 22 Mar 2006 12:40:01 -0800 (PST) From: Bill Schoolcraft X-X-Sender: bill@liam.billschoolcraft.com To: doug@polands.org In-Reply-To: Message-ID: References: <43E48BB8.7000906@infracaninophile.co.uk> System-ID: [en] (SuSE-9.3 64-bit) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-questions@freebsd.org Subject: Re: 6.0, allow remote logging? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Mar 2006 20:40:07 -0000 At Wed, 22 Mar 2006 it looks like Doug Poland composed: > On 2/5/06, Bill Schoolcraft wrote: > >> I've been trying to get 6.0 to allow itself to accept logs. > >> > >> I have a line in /etc/rc.conf that states the remote machine: > >> > >> syslogd_flags="-a 192.168.0.3" > >> > >> I have restarted "syslogd" so the output of "ps -auxw | grep syslog" > >> shows the following: > >> > >> root 21703 0.0 0.3 1296 748 ?? Ss 9:31PM 0:00.03 /usr/sbin/syslogd > -a 192.168.0.3 > >> > >> > > And my 'ps -auxw' output shows syslogd running with the > > "-s " too. I wonder how to trigger that port to receive > > packets. Apparently syslogd believes all is well. :( > > > I'm having the same problem getting syslogd to "work" on a 6.0-STABLE > box. My ps -waux command shows the -a , and sockstat -l > confirms that it's listening on port 514/udp. Logging works from the > localhost only, not from any remote hosts. > Yes, I too had the issue and had to use my SuSE-9.3 box to receive logs... Maybe it's the curse of the "dot-oh" release(s) who knows. -- Bill Schoolcraft | http://wiliweld.com "If your life was full of nothing but sunshine, you would just be a desert."