I thought other might benefit from this lesson learned and thought it maybe should be added to the man-pages.
I thought my network connection was glitchy and hence set rsync up for --timeout=120 but I found out that I was actually causing the glitch with this script: #! /bin/sh - while true; do rsync -avz --progress --timeout=120 --delete /media/rsync_gb01/movies/ myserver:movies; sleep 120; done The problem: When rsync is checking large files it takes time to verify the content at both ends, so when using the option --timeout=TIME both source and destination must be capable of performing the check within the time window provided. For a 2.3 Gb file this check might take 2:30 minutes, so if the option --timeout=120 then rsync will exit before the destination has been able to complete its file check. For the future options: Could/can rsync incorporate the adjustment of timeout to include the time used for the check? Fictive example: --timeout=xfer#1-check-time + 120 seconds? detailed example: me@source:~$ rsync -avz --progress --timeout=xfer#1-check-time+120 --delete /media/rsync_gb01/movies/ myserver:movies sending incremental file list DVD1.mkv 2302868295 100% 14.01MB/s *0:02:36* (xfer#1, to-check=41/286) DVD2.mkv ...and so on... -- Bjorn
-- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html