Dave,
I understand how the timeout works. The problem here is that the traversing
of the directory tree on the client side does indeed take more than 1 hour,
during which no bytes are exchanged on the wire between client and server.
So I do know for a fact that the read call on the server side
You shouldn't need to have such a long timeout. The timeout is not over
the whole length of the run, only the time since the last data was
transferred. It's a mystery to me why it quits after 66 minutes rather
than 5 hours, but the real question is why it stops transferring data for
so long.
On Fri, May 03, 2002 at 04:41:17PM -0500, Dave Dykstra wrote:
You shouldn't need to have such a long timeout. The timeout is not over
the whole length of the run, only the time since the last data was
transferred. It's a mystery to me why it quits after 66 minutes rather
than 5 hours, but
Dear all,
I've been trying to track down a problem with timeouts when pulling data from
an rsync daemon and I have now run out of any useful ideas.
The problem manifests itself when I try to transfer a large directory tree
on a slow client machine. What happens then is that the client rsync
