On Tue, Aug 19, 2014 at 01:59:42AM +0200, Alexander Bluhm wrote:
> I will split this diff into smaller parts to make review and
> discussion easier.
At the moment syslogd opens both IPv4 and IPv6 sockets unconditionally.
I can restrict it to a protocol family with -4 and -6 command line
switches.
On Fri, Aug 22, 2014 at 06:43:47PM +0200, Alexander Bluhm wrote:
> At the moment syslogd opens both IPv4 and IPv6 sockets unconditionally.
> I can restrict it to a protocol family with -4 and -6 command line
> switches. If the log server is a FQDN, DNS chosses wether to take
> the IPv4 or IPv6 rou
On Sat, Aug 23, 2014 at 01:10:52PM +0200, Alexander Bluhm wrote:
> On Fri, Aug 22, 2014 at 06:43:47PM +0200, Alexander Bluhm wrote:
> > At the moment syslogd opens both IPv4 and IPv6 sockets unconditionally.
> > I can restrict it to a protocol family with -4 and -6 command line
> > switches. If th
On Fri, Aug 22, 2014 at 06:43:47PM +0200, Alexander Bluhm wrote:
> At the moment syslogd opens both IPv4 and IPv6 sockets unconditionally.
> I can restrict it to a protocol family with -4 and -6 command line
> switches. If the log server is a FQDN, DNS chosses wether to take
> the IPv4 or IPv6 rou
