Date: Tue, 20 Dec 2016 02:12:34 +0900 (JST) From: Hiroki Sato <hrs@FreeBSD.org> To: imb@protected-networks.net Cc: freebsd-current@freebsd.org Subject: Re: syslogd no longer listens (or sends) on a network socket Message-ID: <20161220.021234.885117715060624657.hrs@allbsd.org> In-Reply-To: <d5c17fa6-ddd7-277f-6f92-ee8fb55cd8fc@protected-networks.net> References: <d5c17fa6-ddd7-277f-6f92-ee8fb55cd8fc@protected-networks.net>
next in thread | previous in thread | raw e-mail | index | archive | help
----Security_Multipart(Tue_Dec_20_02_12_34_2016_348)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Michael Butler <imb@protected-networks.net> wrote in <d5c17fa6-ddd7-277f-6f92-ee8fb55cd8fc@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 ----Security_Multipart(Tue_Dec_20_02_12_34_2016_348)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEABECAAYFAlhYFQIACgkQTyzT2CeTzy20PACeIC2c+U44KtxBHiE113zEJXYw UVIAoMnlob/qAmQSB1bbPEu6aakxGzWV =EO9E -----END PGP SIGNATURE----- ----Security_Multipart(Tue_Dec_20_02_12_34_2016_348)----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20161220.021234.885117715060624657.hrs>