similar to: Patches for OS X.

I've recently encountered this issue which was discussed here about a year ago. I'm not sure if anyone has a fix for this, but I thought I would post my workaround here. Since the topic is old, I'm summarising the problem .. basically it involves rsync creating large numbers of files with a leading ".." when syncing to an apple network share via afp. The essence of the

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

https://bugzilla.samba.org/show_bug.cgi?id=8566 Summary: Spotlight comments (extended attributes) are not synced Product: rsync Version: 3.0.9 Platform: All OS/Version: Mac OS X Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org

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 :

https://bugzilla.samba.org/show_bug.cgi?id=6276 Summary: crtimes.patch does not preserve creation dates on Mac x86_64 only Product: rsync Version: 3.0.6 Platform: x86 OS/Version: Mac OS X Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

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 Rob / Wayne, Sorry for the slow reply Rob. I'm not sure of the requirements for patches, but I think it would be useful to create one for this case as there are reasonably number of people affected. I created a patch file against the current version (see below). Would it be possible to include this patch in the official list? Cheers Ira diff -Naur rsync-3.0.8_orig/receiver.c

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

https://bugzilla.samba.org/show_bug.cgi?id=7685 Summary: rsync should not set the creation data on the root folder of an HFS+ volume Product: rsync Version: 3.0.7 Platform: x86 OS/Version: Mac OS X Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at

Hello all, I was eager to test the fresh release with MacOS X using "bbouncer" This is how I compiled and run the tests: patch -p1 <patches/osx-create-time.diff patch -p1 <patches/fileflags.diff ./prepare-source patch -p1 <patches/backup-dir-dels.diff ./configure make make test sudo make install Then compiling and running "bbouncer" from

First of all. Thank you rsync developers and maintainers for all of your work. It is awesome. I love rsync. I can't thank you enough. So this has been brought up before: https://lists.samba.org/archive/rsync/2010-April/024941.html We are getting this error: stderr: rsync: unpack_smb_acl: sys_acl_get_info(): Undefined error: 0 (0) due to ACL entries that can not be resolved by name at

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

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

Hello, I'm setting up a system for automated synchronization and backup between different macs (OS X Lion 10.7). I use HFS+ Journaled as filesystem. I wanted to follow these guidelines: http://www.bombich.com/rsync.html but I gave a look inside the patches Mr. Bombich suggested and I thought I could try first by using only the normal ones provided by rsync.samba.org, so I skipped curl -o

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"

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

Thanks Wayne and everybody, This is a huge boost to have a modern rsync for OSX. We're all grateful. Rob D PS I did notice that we lost the bsd flags test in 3.0. It was ok in pre10.... thanks again bbouncer Verifying: basic-permissions ... ok Verifying: timestamps ... Sub-test: modification time ... ok ok Verifying: symlinks ... ok Verifying:

I am a developer on the LBackup project. An LBackup user recently posted a question to the mailing list asking about the following error. > "rsync: unpack_smb_acl: sys_acl_get_info(): Unknown error: 0 (0)" Link to thread : <http://www.mail-archive.com/lbackup-discussion at lists.connect.homeunix.com/msg00040.html> My understanding of this error is that when copying files via

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

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