similar to: rsync3 universal binary for Mac OS X?

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

Rsync-2.5.2 does not gracefully report connection and transfer errors and always properly return with a non-zero exit code, despite many assurances to the contrary in the code and commit logs. It seems a kludge to handle a special case of lost connections to older servers was FAR too aggressive! With '-vvv' I also print the source of the exit_cleanup() call, and optionally with

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

for those who care, the yodl pkg, a prereq for building rsync3-cvs docs (& more?), had 'issues' @ version <= v2.04 with building cleanly on osx. it's been updated today to v2.10, http://sourceforge.net/project/showfiles.php?group_id=126615 v2.10 builds clealy, without req'd patching or error, and works just fine when/as used by rsync3 -- or elsewhere.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've compiled rsync 3.0.3 on OSX 10.4 PPC via the plain jane ./configure; make method (no patches). The resulting binary has then been moved to /usr/local/bin/rsync3 and copied to a OSX 10.5.4 Intel client machine as rsync3. I then run the following command: rsync3 -vvv -e ssh -avAX --progress --delete -

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!

I create a new thread, because the issue is not really the same, but i copy here the thread that made me jump into the list. My issue is not really that it waits before starting copying, but a general performance issue, specially when there are multiple rsync running at the same time. Here is my situation : I have multiple clients (around 20) with users and i want to rsync their home dirs with

Hello, Noticed this (bug?) while testing out rsync. For a little background, I need to push files real-time to some front-end servers, and I am thinking of switching from some custom shell scripts that do this job to rsync. I am thinking of running rsync as a daemon on the front-end servers, and doing an upload from the back-end server to push the data out as it comes in. So, here is the deal:

Hi, I've been using rsync (OSX Tiger now Leopard) to backup my home folder daily using -a -H -A -X link-dest=dir to make incremental backups. There was a problem though since many files especially images, movies etc would be recopied each time instead of creating hard links. I have been testing the pre5 release and found that it seems to make hard links correctly for all files. I

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

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

Hi Bryan, thanks for your kind reply but it happend only with some fonts not all font file, (email with attachment is under verification by admin, so i resend this without attachment file) here i attach 2 screenshot one original folder and second backup folder, you can notice that the font .otf, .ttf, .dfont have no problem in rsync it copied as it is but the font that not show extension (Font

hi, as it's been awhile since my last attempts w/ v269, i'm building the latest rsync3-svs on osx 10.4.8; looking to see what's evolved re: acls & xattrs support on osx ... @ build, i note complaint abt a missing yodl2man, which originates with YODL. YODL, then requires icmake. as neither is available on osx, it's src build time. on building debian's icmake (already

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

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

From: Andrea Gelmini <andrea.gelmini at gelma.net> --- rsync3.txt | 22 +++++++++++----------- 1 files changed, 11 insertions(+), 11 deletions(-) diff --git a/rsync3.txt b/rsync3.txt index 42d77dc..293680f 100644 --- a/rsync3.txt +++ b/rsync3.txt @@ -1,6 +1,6 @@ -*- indented-text -*- -Notes towards a new version of rsync +Notes towards a new version of rsync Martin Pool <mbp at

Hi All, I don't know if this has been discussed here but creation dates are nto being preserved on OSX 10.6.1 in 64 bit mode. Rare of course, the folks that are using 64 but I am getting reports. I built in 64 with the usual crtimes and fileflags patches. Otherwise works like a dream and, in 64, is unbelievably Fast! Thanks, Rob

Hi All, I have a client and we are trying to create a backup for several folders on OSX 10.4.11 with rsync 3.0.0pre9. One folder copies fine but the other three generate this error and I am stumped. using: rsync -aHAX --fileflags --crtimes -v we get; sending incremental file list rsync: writefd_unbuffered failed to write 82 bytes [generator]: Broken pipe (32) rsync error: error in

Hi All, I've been off list for a while and just got around to building rsync 3.0.6 on Mac OSX 10.6 intel core 2 duo machine. It runs great on similar machines but someone just said it won't for their OSX 10.6 intel core duo and returns an error: rsync Bad CPU type in executable. I check the file and it says: rsync: Mach-O 64-bit executable x86_64 my older builds all

Hi All, I have been reading about the HFS+ filesystem compression on Snow Leopard and how copying or cloning over system files with rsync and other tools results in them being expanded on destination. I was wondering if there was any thoughts on updating rsync to accommodate this? It is kind of a shame to the lose the benefits of the new compression. Thanks, Rob