X-Spam-Check-By: sourceware.org
Message-ID: <01cc01c66968$50acb950$b5db87d4@multiplay.co.uk>
From: "Steven Hartland" <killing AT multiplay DOT co DOT uk>
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>
Subject: Re: rsync over ssh hang issue understood
Date: Wed, 26 Apr 2006 20:33:31 +0100
MIME-Version: 1.0
Content-Type: text/plain; 	format=flowed; 	charset="iso-8859-1"; 	reply-type=original
Content-Transfer-Encoding: 8bit
X-Mailer: Microsoft Outlook Express 6.00.2900.2869
X-Spam-Processed: multiplay.co.uk, Wed, 26 Apr 2006 20:33:58 +0100 	(not processed: message from valid local sender)
X-MDRemoteIP: 212.135.219.181
X-Return-Path: killing AT multiplay DOT co DOT uk
X-MDaemon-Deliver-To: cygwin AT cygwin DOT com
X-MDAV-Processed: multiplay.co.uk, Wed, 26 Apr 2006 20:33:59 +0100
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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: "René Berber"
>>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/
>>
>> 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 solved
> 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 bytes
> but it receives less.

tcsh is the default shell on FreeBSD which is the "recieving"
end in this test yes but I'm a little confused how the shell
could effect the results of rsync? FreeBSD to FreeBSD for FreeBSD
to Windows SFU doesnt have this issue so something specific to
tcsh on cygwin?

An example of this failure is:
[log]
rsync -av --progress cygwin1:/testdir/ /testdir/
receiving file list ...
1705 files to consider
created directory testdir
/
bf2_w32ded.exe
           0   0%    0.00kB/s    0:00:00
***Hung here***
^CKilled by signal 2.0.00kB/s    0:00:00
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(242) [receiver]
rsync error: unexplained error (code 255) at rsync.c(242) [generator]
[/log]

Even though the destination has now been terminated the
rsync process on the cygwin source box is still sitting
there. Checking on the cygwin box no shell is actually
running.

Interestingly if I try to get a thread dump using
sysinternals process explorer the rsync process goes
mad using all available cpu.

    Steve 



================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 

In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137
or return the E.mail to postmaster AT multiplay DOT co DOT uk.


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