similar to: Rsync 3.0.2 released w/xattr security fix (attn: 2.6.9 onward)

Hello, I've compiled a fresh copy of rsync 3.0.2 (version info below) on MacOSX Leopard Server 10.5.1 and am doing an rsync of the whole system like this: /bin/rsync302 -axX / /Volumes/appserv02/2008-14/ --exclude=/Network --exclude=/net --exclude=/home It works OK, but returns with a failure error code, and the following errors relating to files with sockets. rsync: get_xattr_names:

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

Hello, As i cannot get 3.0.0pre5 to work in my environment (throwing crazy errors which i've posted previously), i would like to revert to 2.6.9 . Of course, the reason i tried to use v3 in the first place was for the acl, xattr, and fake-super options - which, evidently, can be enabled under 2.6.9, as per the following sources: http://lists.samba.org/archive/rsync/2007-February/017218.html

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

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 everyone! FOREWORD: I respect your time and resources, I hope to not bother people on this mailinglist! To my defense: This question is far easier towards humans than to mailinglist and web search-engines as the search terms in relation to each other are highly in-causal or paradoxical, and hence lead to poor results. Of course the manpage was the first place where I looked

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

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, 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=5365 Summary: --backup and --xattrs are not compatible Product: rsync Version: 3.0.0 Platform: x86 OS/Version: Other Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: fauthier@free.fr

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

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

https://bugzilla.samba.org/show_bug.cgi?id=5324 Summary: with option --xattrs the process rsync is more long time Product: rsync Version: 3.0.0 Platform: x86 OS/Version: Other Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: fauthier@free.fr

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

On Tue, Jun 17, 2014 at 11:44:11AM +0200, Paolo Bonzini wrote: > Il 17/06/2014 11:03, David Marchand ha scritto: > >>Unless someone steps up and maintains ivshmem, I think it should be > >>deprecated and dropped from QEMU. > > > >Then I can maintain ivshmem for QEMU. > >If this is ok, I will send a patch for MAINTAINERS file. > > Typically, adding

On Tue, Jun 17, 2014 at 11:44:11AM +0200, Paolo Bonzini wrote: > Il 17/06/2014 11:03, David Marchand ha scritto: > >>Unless someone steps up and maintains ivshmem, I think it should be > >>deprecated and dropped from QEMU. > > > >Then I can maintain ivshmem for QEMU. > >If this is ok, I will send a patch for MAINTAINERS file. > > Typically, adding

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

Applying the xattr and acl patch to 2.6.9, running ./prepare-source and config with ./configure --enable-xattr-support results in a version which fails to transfer with the error msg 'wrong write used in receiver' and complaints about protocol mismatch. I see there's a patch for a similar problem when SUPPORT_ACLS is defined; anybody done one for --xattrs? No, I'm not