Rush Manbert writes:
> > We found this on Linux 2.6 kernel. I'd recommend capturing a trace
> > and examining in wireshark. We tried lots of tcp options, but it
> > couldn't find one that had a useful effect.
> > -Eric
>
> Thanks for the info!
Rush,
For what it's worth, our solution was to set an early timer on
our connect call, and if that timer fires then we close the socket and
try again. We happened to know if the connection was local, and set
the timer differently (0.05 seconds vs 1 second) in that case. It was
an ugly hack.
-Eric
