Date: Tue, 20 Dec 2016 10:12:51 -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: <47083256-c0dd-56db-64c9-33ac43788487@protected-networks.net> In-Reply-To: <20161220.124246.1063562270206163854.hrs@allbsd.org> References: <d5c17fa6-ddd7-277f-6f92-ee8fb55cd8fc@protected-networks.net> <20161220.021234.885117715060624657.hrs@allbsd.org> <da73919b-24bf-7ebf-3809-2220c087ca47@protected-networks.net> <20161220.124246.1063562270206163854.hrs@allbsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/19/16 22:42, Hiroki Sato wrote: > Michael Butler <imb@protected-networks.net> wrote > in <da73919b-24bf-7ebf-3809-2220c087ca47@protected-networks.net>: > > im> On 12/19/16 12:12, Hiroki Sato wrote: > im> > Michael Butler <imb@protected-networks.net> wrote > im> > in <d5c17fa6-ddd7-277f-6f92-ee8fb55cd8fc@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. That works - thanks! :-) Michael
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47083256-c0dd-56db-64c9-33ac43788487>