I'm not Dave Dykstra [[EMAIL PROTECTED]] writes:
> On September 9 Tridge submitted a fix to CVS for that problem. See
> revision 1.25 at
> http://pserver.samba.org/cgi-bin/cvsweb/rsync/generator.c
I'm not sure that fixes the use of the timeout for the overall
process. See a recent answer b
---
Tim Conway
09/20/2001 08:36 AM
To: Scott Howard <[EMAIL PROTECTED]> @SMTP
cc:
Subject: Re: Problem with transfering large files. (Document link: Tim Conway)
Classification: Unclassified
I know that's what the docs say, but I have found that i have to set the timeo
On Thu, Sep 20, 2001 at 08:52:26AM -0500, Carey Jung wrote:
> >
> > Not so.
> >
> > --timeout=TIMEOUT
> > This option allows you to set a maximum IO timeout in
> > seconds. If no data is transferred for the specified
> > time then rsync will exit. The defa
>
> Not so.
>
> --timeout=TIMEOUT
> This option allows you to set a maximum IO timeout in
> seconds. If no data is transferred for the specified
> time then rsync will exit. The default is 0, which
> means no timeout.
>
> The 2400 second timeo
On Mon, Sep 17, 2001 at 12:15:12PM -0600, [EMAIL PROTECTED] wrote:
> Easy enough... look at your parameters. You're saying that you must not transfer
>more than 48kb in a session... you actual mileage will be slightly smaller,
>because of overhead. You have limited yourself to a bandwidth
Easy enough... look at your parameters. You're saying that you must not transfer more
than 48kb in a session... you actual mileage will be slightly smaller, because of
overhead. You have limited yourself to a bandwidth of 200kbps for a duration of
2400 seconds.
A single 400Mb file would ta
