syslogd no longer listens (or sends) on a network socket
Michael Butler
imb at protected-networks.net
Tue Dec 20 00:44:04 UTC 2016
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
More information about the freebsd-current
mailing list