similar to: --link-dest

When using --link-dest, this block of code in skip_file causes new copies of files to be created if source and destination file permissions differ, even if -p -o and -g haven't been specified. if (link_dest) { if((st->st_mode & ~_S_IFMT) != (file->mode & ~_S_IFMT)) { return 0; } if (st->st_uid != file->uid || st->st_gid != file->gid) { return 0; } }

Hello, i'm using rsync 2.6.0 for daily-syncing some remote AIX 5.2 machine to a local linux (RH 7.3) with using the --link-dest option for saving space on incremental backups. Even if there are no changes on the AIX machine, all files are newly transferred on every new sync. My test scenario (actisi=remote aix machine, actisa=local linux machine): =====> Initial rsync [mma@actisa

Hi -- I was very keen to download rsync and give it a whirl with the new --link-dest feature. However, I was terribly puzzled when I couldn't seem to get it working, even though --compare-dest with the same argument would work. It seemed like new files would be transferred even though files existed in the compare-dest/link-dest location; compare-dest would detect them but link-dest would

Please CC me directly as i'm not on the list. I have attached a patch against latest CVS (cvs diff -u) that adds the following functionality. I can break it up if you would prefer it in pieces. Comments welcome. o add compare-perms option This creates a new inode for a file even if only the perms have changed. This way if a file outside of destdir is hardlinked to a dentry inside

Hi all, I recently ran into some problems with rsync. My plan is to renew some of our old administration concepts from early 90's, I already replaced rdist with rsync a few years ago. Because of the rdist legacy, the current method requires synchronizing files into 6 different locations, {/alt,/usr/alt}/{hostdep,sysdep,hutdep}, which in turn are prioritized by a tool that just symlinks

The attached patch adds an option --drop-suid which caused rsync to drop setuid/setgid permissions from the destination files. ie, even if the source file is setuid, the target file will not be. Added as we want to rsync the same files to machines both inside and outside our firewalls. For machines inside the firewall some files should be suid, for machines outside the firewalls they should

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

I posted a patch a few days ago that adds copying of atime. At that time, it was just enabled with -t/--times. After some time, we have figured out that that choice might not have been the best. Here's a new version of the patch (relative to CVS) that adds -A/--copy-atime instead. It also includes a test case. Any feedback on this patch and/or the previous one that I posted?

Hi, How about adding now option '--backup-only' that means making backups only and don't change any destination files? (I posted similar patch a month ago, but the patch was made for nightly snapshot of 20020808, which was tooo old! Laugh at me...) I want to use rsync with LVM snapshot to make incremental backups like below: 1) Make LVM snapshot of file system and mount it.

Updated to current cvs without the --exclude-from - patch. This patch allows specifying a --link-dest path similar to --compare-dest except that unchanged files are hard-linked to the --link-dest path instead of producing a sparse tree. -- ________________________________________________________________ J.W. Schultz Pegasystems Technologies email address: jw@pegasys.ws Remember

Hi, first of all, sorry for taking so long. Unfortunately, some other tasks kept coming up. Anyway, attached is the version of the flags patch, that is based on the one I'm using with 2.6.9. It is against the rsync-3.0.0pre9 release. I've included the option name change from the repository, so the option is now called --fileflags. Improved from the previously distributed version is the

Please CC me. I'm not subscribed. Attached is a patch against 2.5.4pre1 CVS current to add the --link-dest option so rsync will create hardlinks for unchanged regular files to a directory on the destination. This is like --compare-dest except that the result is not a sparse tree. Also included is extension to --(ex|in)clude-from to allow - for stdin. Could one of the maintainers please add

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

Bradley, and the rsync development team, I came across the following message on the rsync bug tracking system, while searching for just this feature (access time preservation)... http://rsync.samba.org/cgi-bin/rsync/incoming?id=2509;expression=atime;user=guest ... where it is written... > Date: Mon, 7 Feb 2000 02:59:42 -0500 > From: "Bradley M. Kuhn" <bkuhn@ebb.org> >

When syncing from Linux to Aix --itemize-changes with --perms lists directories every time because the high-order st_mode bits for directories differ between the two systems, and itemize() isn't masking them with CHMOD_BITS. Here is a fix, tested with 2.6.6pre1. PS: I'm not subscribed to this mailing list, please Cc: if you need more info from me. Thanks. --- generator.c.~1~ Thu Jun

This patch adds the --link-by-hash=DIR option, which hard links received files in a link farm arranged by MD4 file hash. The result is that the system will only store one copy of the unique contents of each file, regardless of the file's name. Anyone have an example of an MD4 collision so I can test that case? :) Patch Summary: -1 +1 Makefile.in -0 +304 hashlink.c (new)

Dear Martin Pool. We regularly use rsync for making backups of our file systems but we have noticed that the atimes are not transferred with the files and are also always updated on the sender's side. Therefore, we have created a modified version of rsync based on rsync-2.6.6 protocol version 29 which transfers the access times with the transferred files and also allows to preserve the access

This patch adds the --link-by-hash=DIR option, which hard links received files in a link farm arranged by MD4 file hash. The result is that the system will only store one copy of the unique contents of each file, regardless of the file's name. (rev 4) * Updated for committed robust_rename() patch, other changes in CVS. (rev 3) * Don't link empty files. * Roll over to new file when

This patch adds the --link-by-hash=DIR option, which hard links received files in a link farm arranged by MD4 file hash. The result is that the system will only store one copy of the unique contents of each file, regardless of the file's name. (rev 3) * Don't link empty files. * Roll over to new file when filesystem maximum link count is reached. * If link fails for another reason, leave

This patch adds the --link-by-hash=DIR option, which hard links received files in a link farm arranged by MD4 file hash. The result is that the system will only store one copy of the unique contents of each file, regardless of the file's name. (rev 5) * Fixed silly logic error. (rev 4) * Updated for committed robust_rename() patch, other changes in CVS. (rev 3) * Don't link empty