On 26 Oct 2000 15:13:28 -0700, Harry Putnam wrote:
> Thanks for the detailed reply. Maybe my trouble can be fixed by upgrading.
>
> > rsync 2.4.1 had known problems with hanging ssh. Are you initiating from
> > the Linux side? I think it only affects the initiating side. Please
> > upgrade to 2.4.6. I believe 2.4.3 was similar to 2.4.6 with respect to ssh
>
> OK, upgrade it is, but do you know of any rpms available? 2.4.4 seems
> to be the most recent rpm shipping with redhat=7.0
Looks like they're on the rsync server at
ftp://rsync.samba.org/pub/rsync/binaries/redhat/
or
http://rsync.samba.org/ftp/rsync/binaries/redhat/
> > but it broke rsh connections. The difference between rsync 2.4.1 and 2.4.3
> > was that 2.4.3 set O_NONBLOCK on stdin & stdout to ssh.
> >
> > And has that ssh been compiled without USE_PIPES?
>
> Ooops ... I'm a little lost as to how to extract that information from
> an rpm binary. Not sure its even possible. Is there a command line I
> can give ssh that will tell one way or the other?
I don't think it's possible; you'd have to use strace or compile it from
source yourself. Chances are it has not been changed to get rid of
USE_PIPES. You may have better luck with an openssh rpm.
- Dave Dykstra
