The ClientTimeOut does what it should do: interrupt the running backup when the TimeOut time has passed and no text is put to stdout. But when you use rsync over SSH, the default settings are '-q' for ssh, which makes the entire backup process go quiet until a share is finished.
Very nice for LAN setups, but unusable for Internet based backups (as they might go like planned at eg 300kbps, but they can also run at 30kbps and then I get an error thanks to the TimeOut setting). What is the easiest way to overcome this? Is there a plan to implement a timeout on file transfer instead of the entire share to backup? Or should I just remove the '-q' option for SSH, and have more overhead on the transport (I assume it is rsync on the client who produces the transfer info)? Please some advice, thanks. -- 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 BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
