This patch contains an rsync 3.0.7 executable for Cygwin with socketpairs
turned off (Pipes are used instead). There are some threads on the net
showing that implementation of socketpairs on cygwin 1.7 may be error-prone:

http://marc-abramowitz.com/archives/2007/10/14/solving-rsync-hangs-with-cygwin/#comment-299686
http://cygwin.com/ml/cygwin/2010-02/msg00700.html
http://www.itefix.no/i2/node/12210

Download!

Apply the patch if you experience problems during rsync transfers and report
your findings and problems at ITeF!x cwRsync forums.

Hi all,

Newbie question for you. I am using cwrsync on windows and I cannot figure out the switch ONLY transfer xml files found in a directory. Is this the correct switch parameters? --include="*.xml"

Thanks,

Brian

 I am using a batch file to backup a directory using cwrsync.  I am using the --link-dest flag to create hard links between my destination folder and another folder previously created with cwrsync.  The batch file runs, but the destination folder created is the same size as the link dest folder.  not sure if it's just not creating the hard links, or if this is and I need a different utility to check the actual size.  here is my command:

rsync -avH --delete --link-dest="\cygdrive\c\testdir\dest\backup.0" source dest\backup.1

thanks in advance!

CHANGES FROM VERSION 4.0.2

 1. UPDATED - Rsync 3.0.7
 
  BUG FIXES:

    - Fixed a bogus free when using --xattrs with --backup.

    - Avoid an error when --dry-run  was trying to stat a prior hard-link file
      that hasn't really been created.

    - Fixed a problem with --compress (-z) where the receiving side could
      return the error "inflate (token) returned -5".

    - Fixed a bug where --delete-during could delete in a directory before it
      noticed that the sending side sent an I/O error for that directory (both
      sides of the transfer must be at least 3.0.7).

Here is the problem.

I have multiple machines that are set to start rsync-client when the machine goes idle.

They do this quite well, and everything works as expected except using the --partial and --partial-dir options (which I could REALLY use).

I know why this is happening but I don't know how to get around it.

The computers are set to run rsync when they go idle, and the scheduled task is set to STOP when the machine is no longer idle.

The process starts up and starts running it's sync, but when the machine is no longer idle, windows kills the task (in a harsh way) for lack of better terms.
I DO want it to stop when not idle, and only run when the computer IS idle.

Rsync never gets to rename the "temp" files into "partial" files for reuse upon the next connection.