similar to: [Bug 14463] New: rsync 3.2.2 server protocol error

https://bugzilla.samba.org/show_bug.cgi?id=13522 Bug ID: 13522 Summary: Patch fileflags.diff and crtimes.diff Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org Reporter:

Returning to this list after a long hiatus: rsync 3 has been working very well for me for many years, as a supplementary backup tool for MacOSX. However, attempting to build the new 3.1.0 release on a brand new Mountain Lion box with my standard 'fileflags' and 'crimes' patches applied, make fails, reporting that 'force_change' is undeclared. In fact, the problem occurs

https://bugzilla.samba.org/show_bug.cgi?id=8019 Summary: Various improvements to the fileflags patch Product: rsync Version: 3.0.8 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: mike at bombich.com

Hi, first of all, sorry for taking so long. Unfortunately, some other tasks kept coming up. Anyway, attached is the version of the flags patch, that is based on the one I'm using with 2.6.9. It is against the rsync-3.0.0pre9 release. I've included the option name change from the repository, so the option is now called --fileflags. Improved from the previously distributed version is the

Hi, Which version of Mac OS X are you running? If you are on Mac OS 10.5.x then I can only suggest that you try either formating the drive to HFS + or creating a disk image with an HFS+ file system. If you are running Mac OS 10.4.x then ensure that that ACL support is enabled on the drive. The following URL contains information on how to check and enable ACL support :

Hi *, it seems rsync with --fileflags isn't able to work on (already) hardlinked and immutable ("schg") files on FreeBSD. The following scripts will create a simple example for this behaviour: -------------------------------------------------------------- #! /bin/sh # # set -x DIR="/var/tmp/rsync_$(date +%s)/" mkdir "${DIR}/" # Preparing dir_A mkdir

Hi All, I just tried (on OS10.5.2) the new fileflags.diff patch patch -p1 <patches/fileflags.diff patch -p1 <patches/crtimes.diff (see result below- I fixed the rej's ) then ./configure make then tried it out but it isn't copying the creation dates now.... just wondering if I missed something .. Rob D robert-dutoits-powerbook-g4-15:rsync-3.0.0pre10 astrid$ patch -p1

Awesome work Wayne. I have been following the various threads about running rsync 3.0.0 on MacOS X 10.4.11 and wanted to confirm that following all the various bits of advice yields a clean running rsync (as tested by backup bouncer). I am running MacOS X 10.4.11 on PPC. The following is a synopsis of my installation procedure (as gathered from the various emails in the archive) - note

Hello, Object of my mail : 1/ stick a problem of incompatibylity between 2 patches (fileflags.diff & detect-renamed.diff) 2/ proposition of a correction I wanted to run rsync on a mac (OS X 10.6.5) with the --detect-renamed option. I therefore tried to compile rsync with the 3 relevant patches : - fileflags.diff - crtimes.diff - detect-renamed.diff But the patch detect-renamed.diff is

Hi Wayne, Trying out 3.1 pre 1 on OSX 10.8.4 I like the new extended stats and the ir-chunk file numbers in log. Also getting a lot of errors and most copies not completing to local disk. rsync just stalls. Standard osx build: patch -p1 <patches/fileflags.diff patch -p1 <patches/crtimes.diff patch -p1 <patches/hfs-compression.diff ./configure make rsync --fileflags --force-change

Hi, I'm trying to make a small script to get rid of Apple's TimeMachine. The aim is to backup the files of my company. I setup a MacMini with a lot of storage attached to it. The MacMini connects every once in a while to our data server (XServe) through SSH and pulls the files that need to be saved (I'm using the --link-dest option to limit the amount of files transferred, and to keep

Hi All, I have had reports of problems with the -R option on OSX 10.6.4. Just tested it myself and found this odd result: When I run this "dtruss -f path/to/rsync -aHAXNR --fileflags --force-change --protect-decmpfs --stats -v /Users/astrid/Documents/main.m /Users/astrid/Desktop/rrr it produces the expected results with the relative folder paths in place

Hello all, I have trouble to use rsync (tested with 3.0.2 and 3.0.3pre2) on MacOS X 10.3. Rsync always seems to stop when working on open files (?). Source is my laptop hard disk, destination a USB attached external drive. If I stop Firefox for instance all runs smoothly. This is how I built rsync: #!/bin/bash # VERSION=3.0.2 VERSION=3.0.3pre2 DIR="rsync-$VERSION"

https://bugzilla.samba.org/show_bug.cgi?id=8266 Summary: fileflags.diff compile fix Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: chris at onthe.net.au QAContact:

What patch files are necessary to build rsync-3.0.9 for OS X 10.6.8 (Darwin 10.8.0)? Mr. Bombich maintains an excellent page about this, but it's a bit out of date, methinks, and his instructions point to patch files that return some interesting errors. My rsync-3.0.9 is working just fine, btw, with the fileflags and crtimes and hfs-compression patches applied; I just wondered if the others

Hi All, I'm trying a remote backup for the first time. It is between two laptops, I installed rsync 3.0.7 on both compiled patch -p1 <patches/fileflags.diff patch -p1 <patches/crtimes.diff patch -p1 <patches/crtimes-64bit.diff patch -p1 <patches/crtimes-hfs+.dif f patch -p1 <patches/hfs_compression.diff ./configure make this all works perfectly for local backups, clones

Hello! I've been trying 3.0.8 on OS X 10.6.7 today and have been getting some errors. The command I'm using is: /usr/local/bin/rsync -aNHAXx --protect-args --fileflags --force-change --progress /Users/davidallie/Documents/ /Volumes/david.allie/Documents/ The target Documents folder is on an iDisk mounted as david.allie . The errors are happening at the beginning and end. BEGINNING:

I compiled 3.0.6pre1, including the crtimes and fileflags patches for use on Intel OS X 10.5.6, as described by Mr. Bombich (thanks!) here: <http://www.bombich.com/mactips/rsync.html> I want to use 3.0.6 because it seems that this bug: <https://bugzilla.samba.org/show_bug.cgi?id=5365> has been resolved (yay!). ----- [~]$ rsync --version rsync version 3.0.6pre1 protocol version 30

For some time now I've been using rsync on FreeBSD to make my system backups. Recently, I accidentally rm'd some files from one directory and I had to go and fetch copies off of my backup drive. After I had done so, I found that about 1/5 of them were corrupted. (They were all .jpg files, by the way.) To be clear, I most certainly *do not* attribute the apparent corruption to rsync.

Dear All, I have been seeing some strange behavior using rsync 3.1.1 on OSX with the 3 standard patches applied when using the --backup and --backup-Dir options. This works as expected on 3.0.9, moving any files on dest that are not on source to the backup folder. If no changes then the backup folder is not even created. -aHAXN --fileflags --force-change --protect-decmpfs ?delete --backup