X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=0.7 required=5.0	tests=AWL,BAYES_50,TW_CG
X-Spam-Check-By: sourceware.org
X-MDAV-Processed: mail1.multiplay.co.uk, Sun, 23 Jan 2011 19:37:17 +0000
X-Spam-Processed: mail1.multiplay.co.uk, Sun, 23 Jan 2011 19:37:17 +0000
X-MDRemoteIP: 188.220.16.49
X-Return-Path: prvs=100478bcf4=killing AT multiplay DOT co DOT uk
X-Envelope-From: killing AT multiplay DOT co DOT uk
X-MDaemon-Deliver-To: cygwin AT cygwin DOT com
Message-ID: <ACB1C810871A40948D282A600A659A25@multiplay.co.uk>
From: "Steven Hartland" <killing AT multiplay DOT co DOT uk>
To: "Jeremy Bopp" <jeremy AT bopp DOT net>, <cygwin AT cygwin DOT com>
References: <4D3BFC69 DOT 7080405 AT cpan DOT org> <4D3C1D54 DOT 7050909 AT cpan DOT org> <4D3C8109 DOT 4030808 AT bopp DOT net>
Subject: Re: failing to clone a git repo via ssh
Date: Sun, 23 Jan 2011 19:37:29 -0000
MIME-Version: 1.0
Content-Type: text/plain;	format=flowed;	charset="iso-8859-1";	reply-type=original
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

----- 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?

    Regards
    Steve


--
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