Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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 10:26:09 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: SSH -R problem Message-ID: <20020410142609.GB15612@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References:

<20020410124650 DOT L1127 AT cygbert DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020410124650.L1127@cygbert.vinschen.de> User-Agent: Mutt/1.3.23.1i On Wed, Apr 10, 2002 at 12:46:50PM +0200, Corinna Vinschen wrote: >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? It's probably the listen in start_thread_socket in select(). The linger value for the dummy socket that gets opened is supposed to be set to zero, though, to eliminate this kind of thing. cgf -- 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/