Re: syslogd no longer listens (or sends) on a network socket

From: Michael Butler <imb_at_protected-networks.net>
Date: Mon, 19 Dec 2016 19:44:00 -0500
On 12/19/16 12:12, Hiroki Sato wrote:
> Michael Butler <imb_at_protected-networks.net> wrote
>   in <d5c17fa6-ddd7-277f-6f92-ee8fb55cd8fc_at_protected-networks.net>:
>
> im> It appears that SVN r309925 and onward no longer opens a network
> im> socket unless the command-line explicitly contains "-b :syslog" :-(
> im>
> im> This also stops one syslog daemon forwarding to another (which is why
> im> I noticed).
> im>
> im> Was this an intentional behaviour change?
>
>  Sorry, it was broken due to another mismerge at r309933.  I fixed it
>  at r310278.  Can you try the latest one and let me know if the
>  problem still persists or not?

No, it does not. "netstat -an -finet | grep 514" shows that it doesn't 
listen on a UDP socket without adding "-b :syslog" to syslogd_flags in 
/etc/rc.conf,

	Michael
Received on Mon Dec 19 2016 - 23:44:04 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:09 UTC