Re: buildfarm server suddenly not talking to old SSL stacks?

Stefan Kaltenbrunner <stefan@kaltenbrunner.cc> writes:
> maybe a more general option to "force ipv4 or ipv6" akin to what most 
> unix networking related utilities support with -4 and -6 might be useful?

+1

> On the other side I wonder whether passing in "MultiHomed" to the 
> IO::Socket::INET6 Constructor behind LWPs back might work - though the 
> docs are pretty light on any details on its actual behaviour:

No, I already looked at the code :-(.  MultiHomed allows it to try
multiple IP addresses obtained from getaddrinfo, but it's already made
up its mind whether to use IPv4 or IPv6, and only addresses of the
given type will be tried.  (The loop logic looks more than slightly
broken, too, at least in the 2.56 version I've got here. I do not think
the author was very clear on whether he needed to handle multiple local
addresses or multiple remote addresses, but AFAICS it will only work
in the unlikely case that you've got *both*, because it loops through
both getaddrinfo results in lockstep.)

> yeah the removal seems easier but do you actually know yet why the 
> system started behaving differently in that regard?

I don't know that it ever was different.  I've never tried to run the
buildfarm client on this machine; I just happened to try the manual
getprint(".../branches_of_interest.txt") invocation that I'd also been
testing on my buildfarm hosts.  Presumably, the RHEL/Fedora machines
that are in the buildfarm have different network environments where it's
not a problem.

            regards, tom lane