Fixing openssh to avoid occasional spurious connection failures

Jonathan Kamens
Wed Nov 7 07:33:00 GMT 2001

>  From: "Robert Collins" <>
>  Date: Fri, 16 Nov 2001 08:51:47 +1100
>  And what about patching cygwin! to automatically retry on EADDRINUSE -
>  if we can detect that the winsock bug is the culprit? That would fix
>  ssh, squid, telnet, ftp....

As I noted in my message to cygwin-developers, I think this is too
hard to patch inside Cygwin.  The problem is that once the failure
occurs, the socket is bound to a particular local port and can't be
rebound to another port, so the socket with the failure is toast.
This means that you'd have to burn down the socket and reconstruct a
new one to retry the failed connection, without the caller ever
noticing.  I don't think it's practical to try to do that.


More information about the Cygwin-apps mailing list