This is the mail archive of the cygwin-developers@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Fixing openssh to avoid occasional spurious connection failures

[Get raw message]
BTW: this is off topic for cygwin-apps. It's either a cygwin@cygwin.com
or a cygwin-dev discussion.(it's not about how to package openssh ).


----- Original Message -----
From: "Jonathan Kamens" <jik@curl.com>
To: <robert.collins@itdomain.com.au>
Cc: <cygwin-apps@cygwin.com>
Sent: Friday, November 16, 2001 8:57 AM
Subject: Re: Fixing openssh to avoid occasional spurious connection
failures


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

Which socket is bound. The cygwin behind-the-scenes win32 socket, or the
openssh/l socket that cygwin manages?

Anyway, I've no intention to try patching this myself, but it does seem
like something that should really be fixed in cygwin, not in n different
client applications.

Rob


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]