similar to: exclude confusion: what does it match against?

When using the rsync server without chroot, the --link-dest and --compare-dest options are almost useless. This is because sanitize_paths is called on the link-dest directory, stripping out leading dots and slashes. Thus, the only possiblitiy for a link-dest directory is under the target directory, which is generally not useful. There doesn't seem to be an easy fix. sanitize_paths is

Hi, I want to rsync a large number of files from A to B, but I need to exclude certain files. Specifically, A has /test/runs/{1,2,3,...,2500}, i.e., about 2500 directories here. However, I only want to transfer the directories that are numbered 2000 or higher, i.e., I want to exclude /test/runs/{1,2,3,...,1999}, so I tried this: rsync --include='/test/runs/***' \

This patch causes --exclude-from and --include-from to read from STDIN when given - for a filename. This was formerly incorporated in my --link-dest patch. Patch against current cvs. -- ________________________________________________________________ J.W. Schultz Pegasystems Technologies email address: jw@pegasys.ws Remember Cernan and Schmitt -------------- next part

Consider the following directory structure /foo/aaa/*/* /foo/bbb/*/* /foo/ccc/*/* I want to sync all of /foo, but exclude /foo/aaa but not exclude any other occurances of "aaa" or "foo/aaa" (be they files or dirs) that might occur within the other dirs /foo/bbb/* /foo/ccc/* etc I don't want to exclude /foo/bbb/aaa or /foo/ccc/111/aaa or /foo/ccc/111/foo/aaa etc...

I'm currently syncing the home directories on two boxes with the syntax: dest-host# rsync -av -e "ssh" --delete --progress source-host:/home/ /home/ That's working well. Now I want to exclude /home/httpd/* from the process. (I don't want web changes on one box to affect the other box.) Which of the following is the best/correct one to use? 1) --exclude=/home/httpd/* 2)

Hi there I have a little problem to get my include / exclude working: I want to sync /etc /home and /usr/local (and all files/dirs beneath) to REMOTEHOST:/dest There are some huge files in /home which I want to exclued I have set up an include/exclude file but I still get too much files. Also the excluded file is synced /usr/bin/rsync -av --exclude-from=excl --delete --numeric-ids --relative

As threatened a while back, there are some exclude/include bugs that I'd like to see fixed in rsync. Here is the patch: http://www.blorf.net/rsync-exclude.patch This fixes the following bugs: - A non-anchored, slash-including pattern with a wildcard needs to be matched at the end of the path (e.g. "CVS/R* should match throughout the tree, not just at /CVS/R*). - A leading

Hi all, I'm trying to made a filtered backup of a windows PC. My target is to create a recursive backup of "only" files reported in the include/exclude files (i.e. only *.txt). the rules (reported below) work well, but also create an empty folders structure that I don'want. Rsync works fine for me (the rules are reported below) except a point, rsync create an empty folders

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

Hello, I'm attempting to update many of my rsync scripts and was trying to hide/exclude absolute files/directories from being sync'd. After reading through the man page section on FILTER RULES, their modifiers, etc., and the mailing list, it seems like the following simple example should work. I'm using the example from the man-page, where it talks about excluding /etc/passwd. In

On Sun, 2007-12-16 at 22:39 +0000, Wayne Davison wrote: > Updated security-release info includes 3.0.0pre7 release. You should make it clear that, even after this fix, daemon-excluded files are still vulnerable to a client that combines a --*-dest or --*-dir above the excluded files (which the filter doesn't prevent) with file-list path information. To close this vulnerability, rsync

Hi Jim. I'm doing custom lowering but here I have a very basic issue and the situation is like this - [Original Op] Mul Dest, Src1, Src2 [Expanded from EmitInstrWithCustomInserter] Step1 Dest, Src1, Src2    <=== BuildMI(..., Step1, Dest).addReg(Src1).addReg(Src2) Step2 Dest, Src1, Src2    <=== BuildMI(..., Step2, Dest).addReg(Src1).addReg(Src2) Step3 Dest, Src2, Src1    <===

This is a patch to add an --rsync-exclude option to rsync-2.5.6cvs. File names in .rsync- (or .rsync+) are excluded (or included) from the file lists associated with the current directory and all of its subdirectories. This has advantages over --cvs-exclude for backing up large file systems since the .cvsignore files only apply to the current directory: unless the .cvsignore restrictions apply

Hi guys, I hope this is not considered a stupid question, but it really seems to be something that needs to be covered with a decent example in the man page. I have looked in every piece of documentation I can think of and have found no answer. So I want to use the multiple link-dest directories feature as of 2.6.4. (I am using 2.6.6) My understanding of how this should work is that I can

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

I just reviewed the EXCLUDE PATTERNS section of the manpage and found that the declarative portion never actually states that only the part of the path that is relative destination is compared. I'm not quite satisfied with my text on this so if anyone has a better way of stating it i'm open to suggestions. Index: rsync.yo

I'm using version 2.6.3 on OS X. I'm trying to use --link-dest to keep some rolling backups of production websites. There is about 2GB of data in 60,000 total files. I do an initial rsync to get an initial copy of the data, and each day thereafter I run rsync again with --link-dest to create a new daily backup. For some reason, in the subsequent runs, rsync updates a whole lot of files

Hello, I am having some trouble matching patterns in targetinstructioninfo.td file with the CodeGen expectation. Could anybody please help? Here is the example: I want to emit instruction for adding 2 different kind of oprands. Basically i want to mix register types when I define the instruction for add,sub etc I define the instruction TargetInstruction.td as follows: class MyInst <opcode

The following is a patch (svn diff) for the R CMD build script that calculates exclude patterns after the tar/untar step rather than before. The perl find() function, used in the calculation of the exclude patterns, ignores symlinks, which meant that directory symlinks were not considered for exclusion. Since the tar/untar step resolves (copies) symlinks, this works around that limitation.

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