similar to: Revised flags patch

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

Working with rsync 3.0.2, it appears that rsync isn't unlocking files before setting the file attributes when those files already exist. This generates error messages on subsequent such as: rsync: rsync_xal_set: lsetxattr("locked_file","test_xattr") failed: Operation not permitted (1) rsync: rsync_xal_clear:

https://bugzilla.samba.org/show_bug.cgi?id=5565 Summary: xattrs not set on locked files that already exist on target Product: rsync Version: 3.0.3 Platform: Other OS/Version: Mac OS X Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

Hi! Using rsync under FreeBSD with hard links and files having schg set result in EPERM "Operation not permitted". This behavior can be observed if rsyncing /usr/bin/. The patch fileflags.diff tries to deal with this situation but changes the flags of the parent directory only. It doesn't change the flags of the files itself. do_link() in syscall.c has to be fixed. The

Hello, I need to run rsync on a mac (OS X 10.6.5) with the --detect-renamed option available. I therefore started to compile rsync with the 3 relevant patches (in my opinion) : - fileflags.diff - crtimes.diff - detect-renamed.diff Here are my exact compile instructions : patch -p1 <patches/fileflags.diff patch -p1 <patches/crtimes.diff patch -p1 <patches/detect-renamed.diff

Hi All! rsync-3.0.6 with fileflags.diff under FreeBSD 8.0-RC1: if there is a file with uchg or schg flag in source directory and it's hard-linked (usual case for /usr/bin), then rsync cannot create the link in destination directory. Error message: rsync: link "/tmp/s/a" => b failed: Operation not permitted (1) The problem is that it's not allowed to link a *chg'ed file.

Looking at http://rsync.samba.org/ftp/rsync/patches/fileflags.diff -- It looks like the changes from fileflags-fixes.diff patch were applied to the patch from http://rsync.samba.org/ftp/rsync/rsync-patches-3.0.0.tar.gz , but this entire chunk of the that original diff file was lost: > diff -up a/config.h.in b/config.h.in > --- a/config.h.in > +++ b/config.h.in > @@ -64,6 +64,9 @@

Some of my users have reported problems with rsync puking on locked folders. The errors typically look like this: rsync -aNHAXx --fileflags --force-change --no-inc-recursive / /Volumes/ Backup > rsync: mkstemp "/Volumes/SCSI Backup/Users/Ken/Library/Caches/ > Metadata/Safari/Bookmarks/..DS_Store.N9xtNy" failed: Operation not > permitted (1) (51) > rsync: mkstemp

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

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

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

I am trying to transfer files between two OSX machines using a FAT32 formatted flash drive. I am transferring a "big" directory (7G). Basically I want to sync everyday my home and work computers for some directories. I tried many possible rsyncs (original supplied, fink 3.0.5/3.0.4 macports 3.0.5, rsync-2.6.3+hfsmode-1.2b2, 3.0.6+fileflags+crtimes) What I would really like to happen

Good day, I am having trouble compiling rsync 3.0.6 on Red hat Linux EL 5.3. I have downloaded 3.0.6, and the patches for 3.0.6. I then do the following: $ patch -p1 <patches/fileflags.diff $ ./prepare-source $ ./configure ?disable-acl-support $ make When I run ./rsync, the following is returned: Capabilities: 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long

I have an rsync daemon running on a FreeBSD 7.3 system. It is running rsync 3.0.4 with fileflags enabled. I have the following six files on it which are all hardlinks and have the immutable flag set: 6830483 -r-sr-xr-x 6 root wheel schg 33268 Jan 6 2005 chfn 6830483 -r-sr-xr-x 6 root wheel schg 33268 Jan 6 2005 chpass 6830483 -r-sr-xr-x 6 root wheel schg 33268 Jan 6 2005

Dear collegaues, please evaluate the patch attached, which allow to use both --detect-renamed and --fileflags extra features. This is meta-patch which sould be applied to detect-renamed. fileflags patch should be applied first, following by the modified detect-renamed patch. It is included in current FreeBSD port, but it seems it would be much more useful to be supported by samba

I've been trying to set up an OpenSolaris-based ZFS NAS server, with one of its functions being a backup server for my Mac-based network. I'm using rsync 3.0.3 pre2 on my Macs with some extended attribute patches, but have been running into some compatibility problems when rsyncing via SSH from a Mac to the Solaris server (I'm not running daemon mode on the server, but rsync 3.0.3 pre2

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

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=12508 Bug ID: 12508 Summary: fileflags & forcechange don't work for hardlinks Product: rsync Version: 3.1.2 Hardware: All OS: FreeBSD Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org