similar to: doc for --compare-dest could be clearer

On Mon, Jun 02, 2003 at 03:32:04PM -0700, Michael Rubel wrote: > Hi J.W., > > Please pardon this intrusion on your private address; the rsync list seems > to be down (no messages since yesterday), so I'm forwarding this directly > to you. If you'd rather wait until the list restarts, that's fine too. I'm CCing the list. > > Best regards, > Mike >

I'm translating rsync.1, and i'm having some problems with the --compare-dest option description, actually i dont understand the part which describes the usefulness of this option, it says : This is useful for doing transfers to a new destination while leaving existing files intact, and then doing a flash-cutover when all files have been successfully transferred (for

Way back: > > ---------- Forwarded message ---------- Date: Mon, 2 Jun 2003 > > 09:56:50 -0700 (PDT) From: Michael Rubel <mrubel at > > galcit.caltech.edu> To: rsync at lists.samba.org Subject: > > --link-dest when target and compare_dir both have file > > > > Hi J.W. et al, > > > > Kevin Everets was kind enough to inform me about some

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

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

Recently various needs for multiple version handling were discussed and I put forward a plan of mine. Subsequently the proposal for a --compare-file=<FILE> switch had support, so I have implemented this. I have also implemented an experimental --compare-auto which decides which file to match against using a rule. Instructions for patch: 1. Install rsync-2.5.6 source 2. "patch -p1

https://bugzilla.samba.org/show_bug.cgi?id=12036 Bug ID: 12036 Summary: Multiple --link-dest, --copy-dest, or --compare-dest flags produce incorrect behavior Product: rsync Version: 3.1.2 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 Component:

Hi, I've been attempting to use --compare-dest DIR SOURCE/ DEST/ If a file exists in DEST but is different to the corresponding file in DIR, then the file is updated in DEST. This is what I would expect. I have found that files which do not exist in DEST but do exist in DIR and SOURCE, are not created. Simply touching the file in DEST causes it to be updated. This behaviour seems

Hi, I just noticed that the value of the '--compare-dest' argument is simply prepended to the DEST argument, even if that has path compnents. For example with this command: rsync -a --compare-dest=$comparedest \ remote::something/1/ \ /local/path/to/1/ if the remote 'something' module has a file called '1/2/3/4/file' (which is going to be mirrored to

Hi all, I have just migrated my tooling from version 2.6.9 to 3.0.0. Unfortunately my script generated an error message during the execution. Because this command was working perfectly in the previous version I suspect this could be a bug. This is the command that I am executing: rsync -av --link-dest=20080313/ --compare-dest=/data/20080313/ 20080313/ /data/20080314/ It just

If I run rsync 2.5.6 not as root, so that the -o (--owner) and -g (--group) flags don't work, then files that are not owned by me in the source directory will not be linked by --link-dest. When rsync looks in my link-dest, it sees a file owned by me. When it compares that with the source file not owned by me, then rsync thinks it cannot skip that file, and no hard link results. However,

https://bugzilla.samba.org/show_bug.cgi?id=1479 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From wayned@samba.org 2004-06-25 19:12 ------- Yes, it certainly can seem counter intuitive that the

https://bugzilla.samba.org/show_bug.cgi?id=1479 Summary: --compare-dest suppresses output file if same timestamp present Product: rsync Version: 2.5.7 Platform: All OS/Version: Linux Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org

https://bugzilla.samba.org/show_bug.cgi?id=9657 Summary: --compare-dest results inconsistent between major 2 and major 3 Product: rsync Version: 3.0.9 Platform: x64 OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org

I must be seriously misunderstanding the man page coverage of --compre-dest. My take was that if a file in compare-dest=dir matches a file in SOURCE/ then it won't be transferred to DEST/. I tried this test. (d1 has single files and 2 subdir with files) cp -a d1 d1a mkdir d2 rsync -avv --compare-dest="./d1a" d1/ d2/ d1a is carbon copy of d1 but still every last file in

Hey. Can anybody spot my mistake? mkdir a b c echo foo > a/test echo foo > b/test rsync -av --compare-dest=b a/ c/ Expected results: no copy of a/test to c/test, since it is already present in b. Actual results: a/test gets copied to c/test What is wrong here? My expectation? my syntax? I'm having the same trouble with --link-dest, and --copy-dest. The behaviour I'm seeing

On Tue, 2008-08-12 at 19:11 +0800, Thomas Gutzler wrote: > I've recently noticed that running rsync -m --compare-dest creates > empty directories, even though it should be prevented by the -m flag. > Try rsync -avm --compare-dest=/path/to/dir/ /path/to/dir/ foo > and you get a nice copy of the directory structure in foo - with no files in it. > I was wondering if there's a

When I'm running "rsync --compare-dest" on a local Linux volume (ext4) it works as expected (duplicate files not created) however when same commands with same options are run on NTFS USB drive (in my scenario below mounted to /share/external/sdt5) all the files are copied regardless if they have been updated or not. I have spent many hours trying to figure out what could be wrong and

https://bugzilla.samba.org/show_bug.cgi?id=5647 Summary: A way to make earlier --compare-dest dirs hide later ones Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org

Hi all. I have just finished a small patch that adds support for multiple --compare-dest or --link-dest args. Its primary usage is to do incremental backups on top of eachother. (My current backup system stores each incremental as a single diff of the latest full.) Example: First full backup: rsync -a somedir full-20040415/ First incremental: rsync -a --compare-dest=../full-20040415 \