I use rsync on Cygwin and have found a new bug in version 2.6.2 that seems to be related to the combination of command line options. I have 2 test cases and 2 machines. Test case 1 succeeds on machine A & B test case 2 fails on machine A (newer rsync) and succeeds on B. Test Case 1 (both machines ok): rsync -v --password-file .rsync.secrets t.txt backupjudi2@host.starfishzone.com::judi2/ Test Case 2 (fails on machine B): rsync -v --modify-window=1 --password-file .rsync.secrets t.txt backupjudi2@host.starfishzone.com::judi2/ Machine A (failing on test 2): Windows XP Home CYGWIN_NT-5.1 judi 1.5.10(0.116/4/2) 2004-05-25 22:07 i686 unknown unknown Cygwin rsync version 2.6.2 protocol version 28 Machine B (both test ok) Windows XP Home CYGWIN_NT-5.1 Dell3 1.5.5(0.94/3/2) 2003-09-20 16:31 i686 unknown unknown Cygwin rsync version 2.5.7 protocol version 26 Error says: @ERROR: auth failed on module judi2 rsync: connection unexpectedly closed (102 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at /home/lapo/packaging/tmp/rsync-2.6.2/io.c(342) I have tried to use the --rsync-path=/SOME/PATH/rsync-debug but this does not go into debug mode nor create a trace file under Cygwin; it seems to ignore the option. Please let me know if this is something I should submit to the Cygwin folk. WORKAROUND: don't use the modify-window option(!)
I am unable to duplicate this using 2.6.3 on cygwin. Do you still see this problem? The only theory I have is that the asprintf() call that is used to create the --modify-window option that is passed to the server was not working right in that build of rsync (or perhaps in that version of cygwin's library?). If you still see the problem, try specifying --max-delete=200 instead of --modify-window=1 and see if there is a problem for that option as well. If so, it is likely to be an asprintf()-related bug.
I haven't been able to duplicate this bug.