Date: Wed, 22 Mar 2006 14:31:18 -0600 From: "Doug Poland" <wisco.disco@gmail.com> To: "Bill Schoolcraft" <bill@wiliweld.com> Cc: freebsd-questions@freebsd.org Subject: Re: 6.0, allow remote logging? Message-ID: <eae8cb0a0603221231w1aeb74fs151b9c89fab1ed6d@mail.gmail.com> In-Reply-To: <Pine.LNX.4.61.0602042329000.16821@liam.billschoolcraft.com> References: <Pine.LNX.4.61.0602032143280.7777@liam.billschoolcraft.com> <43E48BB8.7000906@infracaninophile.co.uk> <Pine.LNX.4.61.0602042329000.16821@liam.billschoolcraft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2/5/06, Bill Schoolcraft <bill@wiliweld.com> 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=3D"-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 <ipaddr>" 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 <ipaddr>, and sockstat -l confirms that it's listening on port 514/udp. Logging works from the localhost only, not from any remote hosts. -- Regards, Doug
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?eae8cb0a0603221231w1aeb74fs151b9c89fab1ed6d>