X-Spam-Check-By:	sourceware.org
Date:	Thu, 27 Apr 2006 18:53:38 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: rsync over ssh hang issue understood
Message-ID:	<20060427165338.GB28583@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<061e01c6694d$18d79e20$a501a8c0 AT CAM DOT ARTIMI DOT COM> <014001c66953$3eeded20$b5db87d4 AT multiplay DOT co DOT uk> <e2ogj9$cnj$1 AT sea DOT gmane DOT org> <01cc01c66968$50acb950$b5db87d4 AT multiplay DOT co DOT uk> <e2okqi$sf9$1 AT sea DOT gmane DOT org> <20060427081642 DOT GA11497 AT calimero DOT vinschen DOT de> <44508D05 DOT 307 AT baltech DOT de> <a5f030530604270450p43f14467r3eaa7bd85dc5a611 AT mail DOT gmail DOT com>
Mime-Version:	1.0
In-Reply-To:	<a5f030530604270450p43f14467r3eaa7bd85dc5a611@mail.gmail.com>
User-Agent:	Mutt/1.4.2i
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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

On Apr 27 07:50, Brett Serkez wrote:
> > If there is something I can do in order to narrow down the problem,
> > please let me know. This issue has already been discussed on the rsync
> > list (https://bugzilla.samba.org/show_bug.cgi?id=2957) and Wayne from
> > the rsync project was quite sure about what he called the "Cygwin's
> > pipe-data bug".
> 
> Yes, this is it.  Reading the above reference, the 2 processes refered
> to on the Cygwin end are ssh and rsync, connected via a local pipe.
> 
> On a Linux/UNIX system the local rsync process would have inherited
> the socket connected to the rsync process on the target and thus the
> two rsync processes would be directly connected over the socket.

Err... that's not right.  When rsync connects over ssh, and then ssh (or
sshd) disappears, who is going to care for the encryption?  You're not
actually supposing the underlying OS socket knows anything about the
ssh protocol, do you?


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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

- Raw text -