Replacing inndstart

[Russ Allbery]

Russ Allbery <rra at Stanford.EDU> writes:

> The trickier problem is this:  It doesn't appear to be possible to tell
> whether the host you're running on actually supports IPv6 without
> actually trying the bind.  getaddrinfo returns both IPv6 and IPv4 even
> if there are no IPv6 interfaces on the host and the kernel doesn't
> support IPv6 (at least under Linux).  This is vaguely annoying with the
> first pass at innbind, since it causes innbind to log noise to syslog
> when the bind fails.

Marco pointed out that my testing methodology was flawed.  The socket
creation does indeed fail if the host doesn't support IPv6, and if the
host supports IPv6 one can successfully bind the socket even if there are
no IPv6-enabled interfaces.

So it doesn't look like we need a silent flag after all; it looks like we
can just always try to bind both IPv4 and IPv6 when built with
--enable-ipv6, skipping IPv6 if the socket creation fails.  Cool.  That
should make this all quite simple, and significantly simpler than what
we're doing now.

-- 
Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>

    Please send questions to the list rather than mailing me directly.
     <http://www.eyrie.org/~eagle/faqs/questions.html> explains why.