On Wed, March 22, 2006 14:40, Bill Schoolcraft wrote: > At Wed, 22 Mar 2006 it looks like Doug Poland composed: > >> On 2/5/06, Bill Schoolcraft <[EMAIL PROTECTED]> wrote: >>>> I've been trying to get 6.0 to allow itself to accept logs. >>>>
>> 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. >> > > 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. > With a little more googlin' and a lot of trial and error, I have it working now... --------------------------------------- in /etc/rc.conf: syslogd_enable="YES" syslogd_flags="-a 192.168.1.0/26:*" --------------------------------------- in /etc/syslog.conf: !* +192.168.1.0/26 *.* /var/log/messages ------------------------------------ [EMAIL PROTECTED] logger -h lebanon -t TEST "from seth" ------------------------------------ [EMAIL PROTECTED] logger -h lebanon -t TEST "from egypt" ------------------------------------ tail /var/log/messages Mar 22 15:40:55 <5.3> lebanon syslogd: exiting on signal 2 Mar 22 15:42:19 lebanon syslogd: kernel boot file is /boot/kernel/kernel Mar 22 15:43:08 192.168.1.12 from seth Mar 22 15:43:39 192.168.1.10 from egypt Not sure why the -t tag didn't come through, but I'm glad to get something anyway. -- Regards, Doug _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
