Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Wed, 10 Apr 2002 12:46:50 +0200
From:	Corinna Vinschen <cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: SSH -R problem
Message-ID:	<20020410124650.L1127@cygbert.vinschen.de>
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<m16v96P-000JyXC AT mail DOT interzone DOT com> <m16vDxH-000JyXC AT mail DOT interzone DOT com>
Mime-Version:	1.0
In-Reply-To:	<m16vDxH-000JyXC@mail.interzone.com>
User-Agent:	Mutt/1.3.22.1i

On Wed, Apr 10, 2002 at 04:59:51AM -0400, Steve Chew wrote:
> 	Thank you for the swift response!  Are you saying that the 
> problem is the the Windows 98 Winsock code?  Lovely...  How would you

It's not restricted to 9x/Me since XP (and W2K) show the same - even
if slightly different - phenomenon.  Looking into the strace shows
that the socket is nonblocking.  I could imagine that a non-blocking
socket is "listening" when read() is called on it for the first time
or something like that.  Who knows how that's implemented in Winsock?

> suggest narrowing down the problem?

I've no idea, currently.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -