On Tue, Jun 13, 2000 at 07:51:33AM +1000, Marc Duponcheel wrote:
> Hi Rsync-ers
>
> Yesterday I read about the odd behaviour of rsync 2.4.3 over rsh
> and a possible workaround (pipe in stead of socketpair).
>
> Indeed pipe gets rid of the abnormal termination (as would
> using the rsync 2.4.1 util.c code I suppose)
The preference for socketpair over pipe was added in 2.4.0. 2.4.2
had nonblocking I/O for stdin & stdout, which caused rsh to terminate
immediately, and 2.4.3 changed that to only stdout.
> but still I get
> something else odd when doing large rsync (which also stops operation)
> Invalid file index -720187932 (count=37122)
That's a similar problem to what many people have reported. Ah, so it is
rsh that has the problem with the non-blocking stdout, not ssh. That makes
a lot of sense. Maybe all we need is to only make stdin and stdout
non-blocking for ssh and not rsh. The trouble is that it is hard to
reliably tell what transport you're using because people can call programs
whatever they want.
> Personally I stick to rsync 2.4.1 (again, over rsh) which has
> never failed for me ...
It does cause ssh to hang.
- Dave Dykstra
