Date: Mon, 19 Dec 2016 19:44:00 -0500 From: Michael Butler <imb@protected-networks.net> To: Hiroki Sato <hrs@FreeBSD.org> Cc: freebsd-current@freebsd.org Subject: Re: syslogd no longer listens (or sends) on a network socket Message-ID: <da73919b-24bf-7ebf-3809-2220c087ca47@protected-networks.net> In-Reply-To: <20161220.021234.885117715060624657.hrs@allbsd.org> References: <d5c17fa6-ddd7-277f-6f92-ee8fb55cd8fc@protected-networks.net> <20161220.021234.885117715060624657.hrs@allbsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/19/16 12:12, Hiroki Sato wrote: > 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? 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?da73919b-24bf-7ebf-3809-2220c087ca47>