On Tue, Jul 11, 2000 at 09:10:12AM +1000, Ned Bass wrote:
> On Tue, Jul 11, 2000 at 07:41:22AM +1000, Dave Dykstra wrote:
> > I have had suspicions that rsync 2.4.3 has hang problems on an rsync server
> > but nobody has confirmed it. I'd like to see somebody try some rigorous
> > server mode tests with the new --blocking-io option that is in rsync CVS.
> > It is defaulted on for rsh as a transport but not for server mode because
> > we hadn't any evidence that server mode was affected. If it's easier for
> > you to hack source code than getting the code out of CVS, instead put
> > "set_blocking(STDOUT_FILENO)" in util.c after the place it does
> > set_blocking(STDIN_FILENO).
>
> OK, I made the above change to 2.4.3 and recompiled. Bingo! I can now
> complete rsync transfers on two separate client/server pairs that were
> previously giving me problems.
>
> Thanks,
> Ned
So it looks like we need to default --blocking-io on also when the remote
side is a daemon! The problem is worse than we thought. Tridge, please
take note and put out a new release soon. Also, please make sure that the
effect on --blocking-io is mentioned in the -e/--rsh man page paragraph.
- Dave Dykstra
