On Thu, Jun 15, 2000 at 08:16:34AM +1000, Mark Milano wrote:
> I have added the line:
>
> set_blocking(STDOUT_FILENO);
>
> to util.c and still get the following:
>
> # rsync -auv snapper:/export/home/mmilano/ /export/home/mmilano/
> sh: rsync: not found
> unexpected EOF in read_timeout
That is unrelated to the thing set_blocking was supposed to fix (which was
the "unexpected tag" errors when using rsh). Rsync must not be in the
default path of rsh on the remote side. You can test that by doing
rsh snapper rsync
and seeing if it says "rsync: not found". You should set --rsync-path to
location where rsync is on the remote side.
> # rsync -auve ssh snapper:/export/home/mmilano/ /export/home/mmilano/
> root's password:
> receiving file list ... done
>
> Giving the -e ssh option seems to work, but then stops at random spots and
> just hangs.
Apparently sshd has a bigger default path and can find rsync on the remote
side. The hanging makes sense, because you need set_nonblocking to be
in effect at least for STDOUT_FILENO. I'm not sure if set_nonblocking is
needed for STDIN_FILENO on ssh too, but one recent report seemed to
indicate that it was, at least for ssh2.
- Dave Dykstra
