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

From: Hiroki Sato <hrs_at_FreeBSD.org>
Date: Tue, 20 Dec 2016 02:12:34 +0900 (JST)
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

Received on Mon Dec 19 2016 - 16:35:46 UTC

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