X-Spam-Check-By: sourceware.org
Date: Thu, 27 Apr 2006 10:16:42 +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: <20060427081642.GA11497@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>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <e2okqi$sf9$1@sea.gmane.org>
User-Agent: Mutt/1.4.2i
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

On Apr 26 15:22, Ren? Berber wrote:
> 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 that
> 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]
> > 
> > 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.

I guess so, too.  tcsh on Cygwin reads its input in textmode, that's
right, but in the problem of the OP tcsh isn't involved.

<rant> The "rsync hangs" problem is not actually a new one.  We had
these reports already ages ago.  However, *nobody* so far having that
problem seem to be willing to actually debug this problem and track it
down.  Grrr.  </rant>


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/