Bill Hoover [[EMAIL PROTECTED]] writes:
> Using an old copy of 2.2.0 (with rsh as the transport) seems to work fine.
>
> Using a new copy of 2.4.3 (with rsh as the transport) works for quite a
> while, then hangs.
When you're building rsync, does it discover and configure to use socketpair
(HAVE_SOCKETPAIR defined in config.h)? If so, one thing you might try as a
test just to see if it makes a difference is undefining that manually.
That'll make rsync use standard pipes again, which should work fine for the
rsh approach. I think the socketpair was an attempt to interoperate better
with later ssh releases, but am not positive. I'm pretty sure that the
issue between pipes, socketpair, and applications like rsh/ssh that
themselves may use one of the two seems to be at the root of a lot of the
flow control and hang issues.
I'm not using an actual rsh utility, but I'm using the rsh portion of rsync
2.4.3 (after undefining HAVE_SOCKETPAIR because that doesn't work properly
under NT) for transfers and have been doing transfers in the 100MB-500MB
range regularly without difficulty. And I needed a 2.4.x release over my
earlier 2.3.2 since that didn't support interleaving stdout and stderr.
-- David
/-----------------------------------------------------------------------\
\ David Bolen \ E-mail: [EMAIL PROTECTED] /
| FitLinxx, Inc. \ Phone: (203) 708-5192 |
/ 860 Canal Street, Stamford, CT 06902 \ Fax: (203) 316-5150 \
\-----------------------------------------------------------------------/
