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: cygwin-developers at cygwin dot com
- Cc: cygwin-developers at cygwin dot com
- Date: 15 Nov 2001 17:41:41 -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> <20011115230625.D27452@cygbert.vinschen.de> <20011115221455.6571.qmail@lizard.curl.com> <20011115233753.E27452@cygbert.vinschen.de>
[Get raw message]
> Date: Thu, 15 Nov 2001 23:37:53 +0100
> From: Corinna Vinschen <vinschen@redhat.com>
>
> Can you give me a pointer to the KB article describing that
> winsock bug?
If there were a KB article about it, my life would have been a lot
easier :-). I couldn't find any evidence in the KB that Microsoft
knows about this bug (or, at least, that they acknowledge publicly
that they know about it).
Like I said in my previous E-mail, I'm going to have our guy with the
MSDN subscription file a support request about the problem, but he's
going to wait until after Thanksgiving to do it (since he's going on
vacation next week and it's not good to file a support request and
then not return their calls about it). I'll keep you posted if/when
we hear something definitive from M$ about it.
jik