On Mon, Oct 16, 2000 at 02:09:52PM +0200, Jan�ke R�nnblom wrote:
>
> Seems like i'm not alone with this issue then. Im using 2.4.6
>
> Im thinking about using rsync to keep a local copy of user
> directories. The users are on a microsoft terminalserver nt4 and the
> target machine is a redhat 7.0.
>
> I use the following syntax:
>
> rsync -e "ssh -l username" -az "/d/home" 192.168.1.1:/rsync/home
> -c --stats -v > c:\sbin\rsync\rslog.txt 2>&1
>
> With a very small amount of files everything goes through but when
> one does increase the files and directories it comes to a halt.
>
> When I switch to 2.3.2 on the client side it works!
>
> I tried with ssh 1.2.26/2.2.0p1 and with rsh. Cygwin 1.1.14 has
> been used to compile rsync for windows nt.
Those of you who are getting a stuck rsync 2.4.6: are you running ssh that
has not been recompiled with "HAVE_SOCKETPAIR" and not "USE_PIPES"? Ssh
1.2.27 configure.in by default always defines "USE_PIPES" which overrides
HAVE_SOCKETPAIR. Andrew Tridgell has said that this change is required
after rsync 2.3.2, although I haven't verified the difference myself: I
went ahead and made the change to ssh's configure.in (and ran autoconf to
regenerate configure) without verifying whether or not it makes a
difference, and I haven't seen any hangs on rsync 2.4.6.
- Dave Dykstra
