We are rsync'ing from an xp box running cygwin to a redhat box, using a Perl script that fist calls for an ssh tunnel, then calls rsync through local host.
ssh -P -f -L 8740:remote.host.ip:873 [EMAIL PROTECTED] -p 22 sleep 25 rsync -vrtz -v --timeout=180 --exclude-from=exludefiles rsync://localhost:8740/<remote path> <target path> ========================================================== This has worked for quite a while on a daily cron job. We can still open the ssh tunnel without any problem. After the tunnel is open and we run rsync, we get the following error messages: rsync error: timeout in data send/receive (code 30) at /home/lapo/packaging/tmp/rsync-2.6.3/io.c(153) rsync: connection unexpectedly closed (598306 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(165) rsync: connection unexpectedly closed (598306 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(165) ========================================================== Then it returns to the command prompt. The number of 'bytes read so far' is not constant on the different times we've tried rsync'ing, but this number does stay around 590kB. Does anybody have any ideas? -- View this message in context: http://www.nabble.com/rsync-error%3A-timeout-in-data-send-receive-%28code-30%29-at--home-lapo-packaging-tmp-rsync-2.6.3-io.c%28153%29-tp17127523p17127523.html Sent from the Samba - rsync mailing list archive at Nabble.com. -- 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