On Mon, Oct 16, 2000 at 07:43:19PM +0200, Jan�ke R�nnblom wrote:
> > 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
>
> I think the above need a bit of clarification (atleast for me). As i
> understand it: ssh should be compiled with HAVE_SOCKETPAIR
> and not USE_PIPES?
That's right. Sorry about the double negative.
> > 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.
>
> Im using openssh2.2.0p1and since i have'nt compiled ssh for
> windows NT myself i cant tell. Im missing some libraries to compile
> it myself but looking in includes.h:
>
> /*
> * Define this to use pipes instead of socketpairs for
> communicating with the
> * client program. Socketpairs do not seem to work on all systems.
> */
> /* #define USE_PIPES 1 */
>
> I'd say USE_PIPES ain't used in my version.
I think that's all it takes for openssh on Unix. ssh 1.2.27 at least had
it defined in configure.in and configure.
I don't know if we have any good data latest-rsync-hanging-over-ssh for NT,
though. I didn't pay enough attention to your first message to realize
that that's what you were using, I was just remembering that a couple other
people had also recently mentioned a hang and I was thinking you might both
be in the same category, sorry.
Eric Whiting's case (rsync 2.4.6 with openssh between Solaris & Linux) is
the one that worries me the most because I thought that was solved and I
have a lot of users using rsync 2.4.6 between Unixes and none have reported
a problem.
- Dave Dykstra
