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

Hiroki Sato hrs at FreeBSD.org
Mon Dec 19 17:35:46 UTC 2016


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?

-- Hiroki
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-current/attachments/20161220/612c61ce/attachment.sig>


More information about the freebsd-current mailing list