OK, I think this is not a (huge) bug .. looking at saned code, it tries to bind v6 and v4 sockets separately. If /proc/sys/net/ipv6/bindv6only isn't set, binding v6 will also bind v4, making the later explicit v4 bind fail.
The second process is probably the one responsible for avahi advertisements.
OK, I think this is not a (huge) bug .. looking at saned code, it tries to bind v6 and v4 sockets separately. If /proc/sys/ net/ipv6/ bindv6only isn't set, binding v6 will also bind v4, making the later explicit v4 bind fail.
The second process is probably the one responsible for avahi advertisements.