X-Spam-Check-By: sourceware.org
Message-ID: <a5f030530604290420i237bc9b0lec43df904f11cf20@mail.gmail.com>
Date: Sat, 29 Apr 2006 07:20:23 -0400
From: "Brett Serkez" <bserkez AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: rsync over ssh hang issue understood
In-Reply-To: <20060428082456.GJ28583@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Disposition: inline
References: <01cc01c66968$50acb950$b5db87d4 AT multiplay DOT co DOT uk> 	 <20060427081642 DOT GA11497 AT calimero DOT vinschen DOT de> 	 <44508D05 DOT 307 AT baltech DOT de> 	 <20060427165032 DOT GA28583 AT calimero DOT vinschen DOT de> 	 <003701c66a2a$2f30b610$b3db87d4 AT multiplay DOT co DOT uk> 	 <20060427184610 DOT GA8203 AT trixie DOT casa DOT cgf DOT cx> 	 <004901c66a2c$ab0d03e0$b3db87d4 AT multiplay DOT co DOT uk> 	 <20060427190910 DOT GB8203 AT trixie DOT casa DOT cgf DOT cx> 	 <007901c66a2f$03c81810$b3db87d4 AT multiplay DOT co DOT uk> 	 <20060428082456 DOT GJ28583 AT calimero DOT vinschen DOT de>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k3TBKYHj003266

<snip>
> This is really a tricky problem.  What I could do to circumvent this at
> least for connections over ssh is to upload an OpenSSH test version
> which uses socketpairs instead of pipes for the local connection to the
> applications.  This avoids using pipes which are the culprit here,
<snip>

This thread's subject line is a reply to my original posting in
December of last year:

http://www.cygwin.com/ml/cygwin/2005-12/msg01096.html

Rereading that posting, I was able to get rsync over ssh to work
reliably by changing rsync to use a pipe vs. a socketpair.  This
solution uses socketpairs instead of pipes.

I'm wondering if there are two pipes/socketpairs?  My read is that
each of the two solutions, essentially matches one to the other.  That
is changing OpenSSH to use socketpairs, matches to rsync's use of
socketpairs and visa versa.

Brett

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