To: cygwin@cygwin.com
From: =?ISO-8859-1?Q?Ren=E9_Berber?= <r.berber@computer.org>
Subject:  Re: rsync over ssh hang issue understood
Date:  Wed, 26 Apr 2006 14:10:34 -0500
Lines: 24
Message-ID: <e2ogj9$cnj$1@sea.gmane.org>
References:  <061e01c6694d$18d79e20$a501a8c0@CAM.ARTIMI.COM> <014001c66953$3eeded20$b5db87d4@multiplay.co.uk>
Mime-Version:  1.0
Content-Type:  text/plain; charset=ISO-8859-1
Content-Transfer-Encoding:  quoted-printable
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
In-Reply-To: <014001c66953$3eeded20$b5db87d4@multiplay.co.uk>
OpenPGP: url=hkp://random.sks.keyserver.penguin.de
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Steven Hartland wrote:

> Just to back this up, we cant get basic rsync to run reliably
> using cygwin either. The command being tested is run from a
> FreeBSD box with the source being a cygwin box using cygwin
> 1.5.19-4:
> rsync -av cygwin1:/testdir/ /testdir/
>=20
> The result is it will randomly hang on a file, no output / error
> returned just stops.
[snip]
> tcsh                    6.14.00-5          OK

While testing is csh involved?

Your description above is very close to a problem with cvs reported and sol=
ved
recently by Jay Abel.  In short, tcsh at the receiving end is changing \r\n=
 to
\n inside binary files, so the receiving process waits for the expected byt=
es
but it receives less.
--=20
Ren=E9 Berber


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