X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.6 required=5.0	tests=AWL,BAYES_00,TW_CG
X-Spam-Check-By: sourceware.org
Message-ID: <4D3C84AF.2060303@bopp.net>
Date: Sun, 23 Jan 2011 13:42:39 -0600
From: Jeremy Bopp <jeremy AT bopp DOT net>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: failing to clone a git repo via ssh
References: <4D3BFC69 DOT 7080405 AT cpan DOT org> <4D3C1D54 DOT 7050909 AT cpan DOT org> <4D3C8109 DOT 4030808 AT bopp DOT net> <ACB1C810871A40948D282A600A659A25 AT multiplay DOT co DOT uk>
In-Reply-To: <ACB1C810871A40948D282A600A659A25@multiplay.co.uk>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

On 01/23/2011 01:37 PM, Steven Hartland wrote:
> ----- Original Message ----- From: "Jeremy Bopp" <jeremy AT bopp DOT net>
>> All of these combinations avoided the early EOFs problem no matter how
>> many times I repeated my testing.  As cgf said, this does appear to be a
>> problem in Cygwin's pipe code, but it's very strange that it only seems
>> to be triggered with Cygwin's git + Cygwin's ssh.  My guess is that
>> there is some kind of race condition in the pipe setup code when both
>> ends of the pipe are Cygwin processes, but I'm admittedly unfamiliar
>> with Cygwin's pipe code.
> 
> Possibly the same issue which still plagues rsync under cygwin?

I've thought the same thing myself, but I don't have any test cases for
that and haven't experienced the problem directly.  As I recall, the
rsync case manifests as a hang which seems a bit different than this
case of unexpected EOFs.  It's possible that it could be rsync's
reaction to the unexpected EOF could mask it as a hang, I suppose.

-Jeremy

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple