>
> Specifically, it seems to me that we should distinguish (at least)
> among the following situations for long dump/restore times
> 1. Large backups/slow links - here...
> 2. Disconnected PC or newly degraded link speed - here it would be
> nice to have a separate "timeout"...
>
> 3. Rebooted PC - in this case it may depend on the backup method. For
> 'rsync' you might as well stop ...
>
> 4. Hung backup - here you want to stop if no "activity" (e.g., no
> information) is being transferred ...
>
>
maybe the timeout should actually run a script and proceed based on the
response. have the timeout set low and run a script to check the bandwidth
usage of that process, then let the timeout period run again and compare the
bandwidth. This would compensate for a large file as there would be
bandwidth used for the rsync process and allow a quick termination if there
is no network connectivity anymore.
thoughts?
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.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/
