Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Hannu E K Nevalainen \(garbage mail\)" To: "ML CygWIN" Subject: RE: rsync protocol error Date: Sat, 27 Sep 2003 22:34:27 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal In-Reply-To: <3F755A45.8030003@ntlworld.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 > From: Mark Thornton > I am attempting to use rsync 2.5.6 to transfer files between two XP > machines. On one machine rsync is run as a daemon (either via cygrunsrv > or just from a bash shell). A copy of a small number of files from the > daemon machine to my local machine has succeeded, however all attempts > to transfer anything in the other direction result in a protocol error: > > $ rsync --verbose * thornton::test/test > rsync: connection unexpectedly closed (28 bytes read so far) > rsync error: error in rsync protocol data stream (code 12) at > /tmp/rsync-2.5.6/i > o.c(165) > > Any suggestions welcome. > > Mark Thornton Use e.g. Ethereal (with the pcap library) and catch the TCP transfers for both the successful direction of the copy, and then for the unsuccessful. Use SMALL file(s). Start two copies of ethereal and compare. (http://www.ethereal.com - free software) This requires a BASIC understanding of the TCP packet structure from you. I would say that you can get very far _without_ TCP expertise. /Hannu E K Nevalainen, B.Sc. EE - 59°16.37'N, 17°12.60'E -- UTC+01, DST -> UTC+02 -- --END OF MESSAGE-- -- 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/