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

Michael Butler <imb_at_protected-networks.net> wrote
  in <da73919b-24bf-7ebf-3809-2220c087ca47_at_protected-networks.net>:

im> On 12/19/16 12:12, Hiroki Sato wrote:
im> > Michael Butler <imb_at_protected-networks.net> wrote
im> >   in <d5c17fa6-ddd7-277f-6f92-ee8fb55cd8fc_at_protected-networks.net>:
im> >
im> > im> It appears that SVN r309925 and onward no longer opens a network
im> > im> socket unless the command-line explicitly contains "-b :syslog"
im> > :-(
im> > im>
im> > im> This also stops one syslog daemon forwarding to another (which is
im> > why
im> > im> I noticed).
im> > im>
im> > im> Was this an intentional behaviour change?
im> >
im> >  Sorry, it was broken due to another mismerge at r309933.  I fixed it
im> >  at r310278.  Can you try the latest one and let me know if the
im> >  problem still persists or not?
im>
im> No, it does not. "netstat -an -finet | grep 514" shows that it doesn't
im> listen on a UDP socket without adding "-b :syslog" to syslogd_flags in
im> /etc/rc.conf,

 Thank you for the report.  I misunderstood what was wrong and fixed
 it just now.  Please try r310310.

-- Hiroki