X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: =?ISO-8859-1?Q?Ren=E9_Berber?= <r DOT berber AT computer DOT org>
Subject:  Re: rsync over ssh hang issue understood
Date:  Wed, 26 Apr 2006 15:22:45 -0500
Lines: 36
Message-ID: <e2okqi$sf9$1@sea.gmane.org>
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>
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: <01cc01c66968$50acb950$b5db87d4@multiplay.co.uk>
OpenPGP: url=hkp://random.sks.keyserver.penguin.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

Steven Hartland wrote:
[snip]
> 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?

Yes, the problem with cvs (actually cvs over ssh) was caused by the shell t=
hat
starts the remote ssh process.

> 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]
>=20
> 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.

Then it must be something different.
--=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/