Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Thu, 15 Nov 2001 23:37:53 +0100
From: Corinna Vinschen <vinschen AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Re: Fixing openssh to avoid occasional spurious connection failures
Message-ID: <20011115233753.E27452@cygbert.vinschen.de>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
References: <20011115213959 DOT 6226 DOT qmail AT lizard DOT curl DOT com> <052f01c16e1f$ffb61890$0200a8c0 AT lifelesswks> <20011115215733 DOT 6471 DOT qmail AT lizard DOT curl DOT com> <20011115230625 DOT D27452 AT cygbert DOT vinschen DOT de> <20011115221455 DOT 6571 DOT qmail AT lizard DOT curl DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20011115221455.6571.qmail@lizard.curl.com>; from jik@curl.com on Thu, Nov 15, 2001 at 05:14:55PM -0500

On Thu, Nov 15, 2001 at 05:14:55PM -0500, Jonathan Kamens wrote:
> >  Date: Thu, 15 Nov 2001 23:06:25 +0100
> >  From: Corinna Vinschen <vinschen AT redhat DOT com>
> >  
> >  Don't think so.  I think we could find a workaround by assigning
> >  local socket numbers in another range (>32768 or so).
> 
> This will not solve the problem.
> 
> If you read my test program, you will see that I am calling bind() on
> the socket before connect(), and the bind() succeeds *** even though
> the connect subsequently fails with WSAEADDRINUSE ***.  So there's no
> way to detect that winsock has assigned an in-use port to the socket
> until it's too late.

Can you give me a pointer to the KB article describing that
winsock bug?

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.