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: Jonathan Kamens <jik at curl dot com>
- To: robert dot collins at itdomain dot com dot au
- Cc: cygwin-developers at sourceware dot cygnus dot com
- Date: 15 Nov 2001 17:09:27 -0500
- 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> <059601c16e21$f088d540$0200a8c0@lifelesswks>
[Get raw message]
> From: "Robert Collins" <robert.collins@itdomain.com.au>
> Date: Fri, 16 Nov 2001 09:07:38 +1100
>
> 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 ).
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