I did look at the code, and it does restart $Conf{ClientTimeout} every time
it sees output from rsync_bpc. Let me see if I can replicate what you
observed.
I agree for rsync it would make more sense to pass that setting onto
rsync_bpc (if it's non-zero), and not set the timeout in BackupPC_dump.
Craig
On Wed, Apr 26, 2017 at 10:19 AM, ACR ACR <[email protected]> wrote:
> From doc:
> Timeout in seconds when listening for the transport program's (smbclient,
> tar etc) stdout. If no output is received during this time, then it is
> assumed that something has wedged during a backup, and the backup is
> terminated.
>
> This is not true for rsyncd method, in my test this setting work like hard
> abort regardless of data activity.
>
> And here some questions:
>
> is rsync-bpc-3.0.9.6 and cygwin-rsync support "normal" rsync parameters:
>
> --timeout=TIMEOUT - timeout that work as expected on IO stale
> -z - compression
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> BackupPC-users mailing list
> [email protected]
> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki: http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
BackupPC-users mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
