X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.4 required=5.0 tests=AWL,BAYES_00,DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED,RP_MATCHES_RCVD,SPF_HELO_PASS
X-Spam-Check-By:	sourceware.org
To:	cygwin AT cygwin DOT com
From:	Richard Ivarson <RiIvarson AT gmail DOT com>
Subject:	Rsync stops with time-out: solved
Date:	Fri, 26 Oct 2012 12:17:34 +0200
Lines:	45
Message-ID:	<k6do18$sa8$1@ger.gmane.org>
Mime-Version:	1.0
User-Agent:	Mozilla/5.0 (Windows NT 5.1; rv:10.0.9) Gecko/20121011 Thunderbird/10.0.9
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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

Just in case other Cygwin users also have this problem, I'd like to describe 
a solution.

The Problem was this:

* Run "rsync" on two Windows XP computers communicating to each other 
directly via the (TCP) network.
Example: Source computer uses rsync to sync several folders with many files 
to a destination computer where a rsync background process is running 
(started via "rsync --daemon").
* After syncing a while there's always a time-out (not always at the same 
file however) and both rsync programs stop to transfer any data. Even a rsync 
started with "-vv" parameter for verbose output doesn't show any progress 
anymore.

* I tried to encircle the problem (see here for example: 
http://cygwin.com/ml/cygwin/2012-03/threads.html#00209 ) but found no 
solution whatsoever.


So:
a) The direct TCP network communication failed for my two rsync programs all 
the time but on different parts of the synchronisation.

b) Then I tried the other variant of Rsync: a remote-shell program as 
transport. You start a SSH background process on the destination machine 
(named "sshd" in Cygwin's sbin folder) and then run rsync on the source 
computer with single colon URLs instead of two colons as in variant a). 
Please see Rsync manual:

"There are two different ways for rsync to contact a remote system: using a 
remote-shell program as the transport (such as ssh or rsh) or contacting an 
rsync daemon directly via TCP. The remote-shell transport is used whenever 
the source or destination path contains a single colon (:) separator after a 
host specification. Contacting an rsync daemon directly happens when the 
source or destination path contains a double colon (::) separator after a 
host specification, OR when an rsync:// URL is specified..."


So, with the ssh variant rsync works now fine on my machines. If anybody else 
has these problems of a) too, maybe variant b) works for you, too?


P.S. Since I'm no network expert at all, does anybody have an idea why 
variant a) doesn't work, but variant b) work well? It's a mystery to me.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -