On Thu, Nov 15, 2001 at 04:57:33PM -0500, Jonathan Kamens wrote: > > From: "Robert Collins" <[EMAIL PROTECTED]> > > 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.
Don't think so. I think we could find a workaround by assigning local socket numbers in another range (>32768 or so). Anyway, why of all numbers "4"??? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:[EMAIL PROTECTED] Red Hat, Inc.