On Fri, Jun 09, 2000 at 02:56:35PM +1000, Bill Hoover wrote:
> I submitted this on the bug tracking as 2634 in incoming, if you want the
> full test.
> I am just now trying to set up using rsync to mirror several gigabytes
> between San Jose and Taiwan.  We have our own 384K link with ping times
> as follows:
> 
> poly-av2.0> ping -s twn344
> PING twn344: 56 data bytes
> 64 bytes from twn344 (158.140.194.175): icmp_seq=0. time=188. ms
> 64 bytes from twn344 (158.140.194.175): icmp_seq=1. time=161. ms
> 64 bytes from twn344 (158.140.194.175): icmp_seq=2. time=159. ms
> 
> Using an old copy of 2.2.0 (with rsh as the transport) seems to work fine.
> 
> Using a new copy of 2.4.3 (with rsh as the transport) works for quite a
> while, then hangs.
..


That's a new one; I hadn't heard anybody reporting hangs with rsh on 2.4.3.
The buffering in rsync was significantly changed in 2.4.0 to remove a hack
that was thought to only help with ssh hangs (and didn't always work).

Please also supply the state of the send/receive queues shown with netstat
on the two ends, in accordance with this announcement sent by the author
of rsync when announcing the 2.4.3 release:

    Finally a plea. When reporting a freeze _please_ include the following
    or we can't help:

    - what is the state of the send/receive queues shown with netstat on
      the two ends.
    - what system call is each of the 3 processes stuck in. Use truss on
      solaris or strace on Linux.

    that info gives us the basic knowledge to categorise the problems and
    work out a fix. Many people seem to be assuming there is just one bug
    that needs fixing. That is defiately _not_ the case. There are
    numerous bugs that each give the symptoms of a freeze. The bugs are at
    the TCP level, the syscall level, the application transport level (rsh
    and ssh) and in rsync.  rsync 2.4.3 is my best effort to address the  
    problems that are fixable within rsync, but without the above info I  
    don't have the basic knowledge to tell which part of the system the   
    bug is in. That means I have to guess - and guesswork leads to errors.


- Dave Dykstra

Reply via email to