Re: [Exim] [BUG?] 3.32: IPv6 changes cause Exim to not start

A long time ago, in a galaxy far, far way, someone said...

> Yeah. It looks like the code for handling that has just fallen out
> somehow. You'll have the same problem on a machine that has IPv6 but
> not IPv4. I think the right thing to do is to make it non-fatal
> (maybe even not deserving of a warning) if any individual socket
> creation fails, and to add a separate check that at least one socket
> was successfully opened.

My thought as well. That's why I'm reporting this to the Exim list rather
than someplace else :)

> >50 accept() failures: Invalid argument
>
> I don't see that here. It usually means you have some kind of version skew
> between the kernel and/or glibc you are using at run-time and the one you
> compiled against.

Unlikely - I got those errors on the same computer I compiled Exim on.
There is only one copy of the C library (glibc or otherwise) installed.


Phil