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: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Message-ID: <052f01c16e1f$ffb61890$0200a8c0@lifelesswks> From: "Robert Collins" To: "Jonathan Kamens" , References: <20011115213959 DOT 6226 DOT qmail AT lizard DOT curl DOT com> Subject: Re: Fixing openssh to avoid occasional spurious connection failures Date: Fri, 16 Nov 2001 08:51:47 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 15 Nov 2001 21:51:54.0314 (UTC) FILETIME=[BD5D62A0:01C16E1F] === ----- Original Message ----- From: "Jonathan Kamens" To: Sent: Friday, November 16, 2001 8:39 AM Subject: Fixing openssh to avoid occasional spurious connection failures > As I just noted in > , > ssh connections from Cygwin can occasionally fail because a winsock > bug causes the connection to be assigned a local port number which is > already in use. > > The simplest workaround for this problem would be to put a default > "ConnectionAttempts 4" setting in the ssh_config that gets generated > by ssh-host-config. > > The next simplest workaround would be to get the OpenSSH maintainers > to apply this patch: 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.... Rob