Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: 15 Nov 2001 17:09:27 -0500 Message-ID: <20011115220927.6541.qmail@lizard.curl.com> From: Jonathan Kamens To: robert DOT collins AT itdomain DOT com DOT au CC: cygwin-developers AT sourceware DOT cygnus DOT com In-reply-to: <059601c16e21$f088d540$0200a8c0@lifelesswks> (robert DOT collins AT itdomain DOT com DOT au) Subject: Re: Fixing openssh to avoid occasional spurious connection failures 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> <059601c16e21$f088d540$0200a8c0 AT lifelesswks> > From: "Robert Collins" > Date: Fri, 16 Nov 2001 09:07:38 +1100 > > BTW: this is off topic for cygwin-apps. It's either a cygwin AT cygwin DOT com > or a cygwin-dev discussion.(it's not about how to package openssh ). Yes, I know. That's why I started two different threads, one on cygwin-developers about the problem itself and one on cygwin-apps about how to fix it in ssh. You're the one who started discussing the underlying problem on cygwin-apps, not me :-). > Which socket is bound. The cygwin behind-the-scenes win32 socket, or the > openssh/l socket that cygwin manages? The Windows socket. jik