dan wrote: > maybe set a rediculously large timeout for backuppc and set the rsync > option --timeout and see if rsync manages it better. i think that > rsync's --timeout option looks for activity not just completion so it > wont timeout on a large file while backuppc looks just for activity > across the ssh link, which is quiet -q so large files eaily reach that > timeout. > > im not sure what removing the -q will do to your backups but it might > see that verbosity as part of a file stream and corrupt the files. > > anyone else have a clue on this? Removing '-q' in the RsyncClientCmd does not interfere with ClientTimeout (just checked it with a ClientTimeout of 20s on a backup with lots of small files (/etc), and it just aborted after 20s while there were still files to transfer).
So I hope there is some other solution than 'huge values for ClientTimeout' as I use now. As a result, I will only be notified of non-working backups after this huge timeout (4 days I use now), instead of having a report on really failed backups (transfer stalls etc). -- Toni Van Remortel Linux System Engineer @ Precision Operations NV +32 3 452 92 26 - [EMAIL PROTECTED] ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ 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/
