similar to: DO NOT REPLY [Bug 6276] New: crtimes.patch does not preserve creation dates on Mac x86_64 only

Wayne, I tried changing "unsigned long" to "uint32" as you suggested, but that doesn't work. The compiler adds padding to the struct to make the fields 64-bit aligned and it has the same problem. ?To convince the compiler that the timespec really should come immediately after the length, the struct can be packed with the pragma pack directive. ?I tested the following, and

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

I've been getting spurious unnecessary copying of files on OSX when using the crtimes patch and the --crtimes -H options (version 3.0.4). I can reliably demonstrate it (on OSX 10.5) by doing this several times (as root): rsync -v -N -axHAX --delete-during --fileflags --force-change /usr/ bin/ /tmp/foo/ I think I've tracked it down to the hard-link processing code in

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:

On a PPC machine running Mac OS X, I noticed that creation time is not preserved for files that are transferred (i.e. versus files that are not transferred, or files that have only attribute changes). I discovered two things that work together to cause this: 1) cmp_time (util.c) doesn't check for negative values provided in file1 or file2. If file2 is positive, and file1 is

Hi All, I promise I won't bug you anymore about this but I did find that the compiled universal binary on rsync3.0.pre10 does preserve creation dates across platforms with the old osx-create-time.diff patch but not with the crtimes patch. If anyone has a clue about this I would be happy to fix it. Thanks again Rob D PS so close!

Hi Jason, Here's rsync10.3xattr_supportv0.6.diff. You can find fileflags.diff and crtimes.diff (that are not from me, but I strongly recommend you to install) here: http://samba.anu.edu.au/ftp/rsync/src/rsync-patches-3.0.5.tar.gz As you could see in the mail from the mail-list, this version have a bug with filenames containing slashes ("/"). They are converted to colons

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 All, Well, we compiled pre9 on an intel Mac running Tiger and now it does work on the machine. I need to see if that will now work on a PPC mac though. Hopefully it will but I am wondering if there is a way to compile and make a universal binary rsync for the Mac that will run on both, from my PPC Mac. Itried that yesterday with patch -p1 <patches/flags.diff patch -p1

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

I have also been eager to test bbouncer The latest source passes with flying colours! but make check finds some problems with xattrs if not run by sudo I have xattr in /usr/local/bin/ from the source found at: http://dev.bignerdranch.com/public/bnr/eXttra.zip What I did: cd /usr/local/Source rsync -av --exclude=.git/ rsync://rsync.samba.org/ftp/unpacked/rsync . rsync -av --exclude=.git/

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

Precisions: If I run my patched rsync on 10.4 instead of 10.3, it's my function that returns an error: rsync: rsync_xal_set: lsetxattr("Src/60-bsd-flags/dir-with- flags","com.apple.FinderInfo") failed: Unknown error: -5000 (-5000) And error -5000 means: afpAccessDenied -5000 User does not have the correct access to the file Directory cannot be shared Available in Mac OS

Hello group, I have an OSX 10.3.9 Server that I'm trying to back up with rsync 3.0.2. Since I didn't have any luck with the 10.3.9 patch and I do have 10.4 clients, I decided to try running the backup over AFP (Apple's file sharing protocol). I found a way to mount the AFP volume with root permissions and rsync 3.0.2 works very nicely using this on the 10.4 clients, preserving

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

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'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

I've just released rsync 3.0.0pre9. We needed one last bug-fix release prior to the 3.0.0 final release, so here it is. I'm not anticipating any large changes prior to that milestone. Please help to test it to ensure that we're ready to go! Send email to the rsync mailing list with your questions, comments, bug reports, etc. You can download the source tar file and its signature

I've just released rsync 3.0.0pre9. We needed one last bug-fix release prior to the 3.0.0 final release, so here it is. I'm not anticipating any large changes prior to that milestone. Please help to test it to ensure that we're ready to go! Send email to the rsync mailing list with your questions, comments, bug reports, etc. You can download the source tar file and its signature