This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: Fixing openssh to avoid occasional spurious connection failures
- From: Corinna Vinschen <vinschen at redhat dot com>
- To: cygwin-developers at cygwin dot com
- Date: Thu, 15 Nov 2001 23:37:53 +0100
- Subject: Re: Fixing openssh to avoid occasional spurious connection failures
- References: <20011115213959.6226.qmail@lizard.curl.com> <052f01c16e1f$ffb61890$0200a8c0@lifelesswks> <20011115215733.6471.qmail@lizard.curl.com> <20011115230625.D27452@cygbert.vinschen.de> <20011115221455.6571.qmail@lizard.curl.com>
- Reply-to: cygwin-developers at cygwin dot com
[Get raw message]
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@redhat.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@cygwin.com
Red Hat, Inc.