Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
Date: 15 Nov 2001 16:57:33 -0500
Message-ID: <20011115215733.6471.qmail@lizard.curl.com>
From: Jonathan Kamens <jik AT curl DOT com>
To: robert DOT collins AT itdomain DOT com DOT au
CC: cygwin-apps AT cygwin DOT com
In-reply-to: <052f01c16e1f$ffb61890$0200a8c0@lifelesswks>
	(robert DOT collins AT itdomain DOT com DOT au)
Subject: Re: Fixing openssh to avoid occasional spurious connection failures
References: <20011115213959 DOT 6226 DOT qmail AT lizard DOT curl DOT com> <052f01c16e1f$ffb61890$0200a8c0 AT lifelesswks>

>  From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
>  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.

  jik