similar to: Manpage states "-C" is an exclude pattern when it's actually a filter rule

Displaying 20 results from an estimated 6000 matches similar to: "Manpage states "-C" is an exclude pattern when it's actually a filter rule"

2014 Aug 07
1
invalid/unknown path to storage
Am I correct: pigeonhole now wants the symlink to the filter file to use an absolute path instead of the relative paths we had? i.e.) sieve-filterfile@ -> /home/mail/domain/user at domain/roundcube.sieve instead of sieve-filterfile@ -> roundcube.sieve Dovecot logs these: dovecot: managesieve(user at domain.org): Warning: sieve-storage: Active sieve script symlink
2010 Jun 06
0
exclude pattern matching rule
this is my file layout how do I write a exclusion pattern matching rule for this? TV_show/ NCIS/ NCIS_LA/ Season 01/ [s01x01].ogv [s01x02].ogv tom_a_sparks
2008 Sep 25
1
INCLUDE/EXCLUDE PATTERN RULES problem on MAC OS
Bonjour, I would like to back up several desktop computer, and notebooks who are running under Mac OS, on a linux server with ext3 filesystem. I try several times with rsync, using include lists ( --include-from=my_include_file). The include list is working except for directory and filename with special character ( like french one : ?,?,? etc ...). The pattern in the include list don't match
2016 May 08
0
[Bug 11909] New: Doc patch for INCLUDE/EXCLUDE PATTERN RULES
https://bugzilla.samba.org/show_bug.cgi?id=11909 Bug ID: 11909 Summary: Doc patch for INCLUDE/EXCLUDE PATTERN RULES Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: core Assignee: wayned at samba.org
2003 Jun 04
1
[rfc idle thought] exclude pattern left anchor
A thought has been nagging me for a bit now so i'll run it up the flagpole and see if anyone salutes. There seems to be quite a bit of confusion regarding the use of the leading slash as a top of tree anchor for exclude patterns. The manpage seems clear enough to me but somehow it doesn't seem to get through. What if we allowed a leading circumflex (^) to serve the same function. We
2003 Nov 11
1
unexpected --exclude pattern behaviours with glob wildcards
Rsync version: rsync-2.5.6-3mdk (Mandrake 9.2) I see from the CVS log that some of the following awkwardness may be fixed (or at least different) in the next public release. I'm looking forward to that. In the interim, here are some problems: --------- Problem 1 - unexpected consequence of replacing / with ** --------- The following exclude works because the explicit slash causes a match
2007 Apr 11
5
Default exclude pattern in 0.9.0
The "rspec" rake task collects all _spec files in the spec directory, and excludes the "watir" directory. Is this indicating a preference for using Watir over Selenium? I would like it better to standardize on something more neutral, ''ui'' perhaps? /Marcus -- Marcus Ahnve http://marcus.ahnve.net
2013 May 15
3
exclude a pattern but only in the top level
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...
2004 Nov 20
7
Importing into rc.firewal rules
I have a grown list of IPs that I am "deny ip from ###.### to any". Infected machines, hackers, etc.. Is there a way to have this list outside of rc.firewall and just read it in?
2005 Apr 17
0
tc-filter Manpage?
Hi, Can anybody point me to some articles that discuss how to use the tc-filter? The man page is still not ready on lartc.org Thanks, Leo
2018 Jun 10
1
[Bug 13467] New: an xattr filter rule is treated as a file filter rule on the remote side
https://bugzilla.samba.org/show_bug.cgi?id=13467 Bug ID: 13467 Summary: an xattr filter rule is treated as a file filter rule on the remote side Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW Severity: major Priority: P5 Component: core
2008 Jan 14
0
[LLVMdev] llvm-gcc miscompilation or it's the gcc's rule?
I don't think C has a way to express 32b x 32b -> 64b multiply, even though there is (on x86 anyway) a hardware instruction that does it. The type of your expression (x * y) is still uint32_t. The implicit type coercion up to uint64_t as part of the return statement doesn't change this. On Jan 13, 2008, at 10:29 PM, Zhou Sheng wrote: > Hi, > > Here is C function: >
2018 Apr 29
3
bug: xattr filter rule treated as file filter rule on the remote side
Summary: an xattr filter rule (e.g. --filter='-x! user.*’, which is suggested by the documentation) is treated as a file filter rule on the remote side. Repro #1, sender is local: host1$ rsync --filter=‘-x! user.*' -avvvHX --delete /tmp/test/. host2:test ... [Receiver] add_rule(-! user.*) Repro #2, sender is remote: host1$ rsync --filter=‘-x! user.*' -avvvHX --delete host2:test/.
2008 Jan 14
3
[LLVMdev] llvm-gcc miscompilation or it's the gcc's rule?
Hi, Here is C function: uint64_t mul(uint32_t x, uint32_t y) { return x * y; } current llvm-gcc-4.0 with -O3 will compile it to: define i64 @mul(i32 %x, i32 %y) nounwind { entry: %tmp3 = mul i32 %y, %x ; <i32> [#uses=1] %tmp34 = zext i32 %tmp3 to i64 ; <i64> [#uses=1] ret i64 %tmp34 } This seems incorrect. I think it should extend %x, %y to i64 first and
2005 Nov 14
0
How to exclude multiple probe patterns ?
Hi, Suppose we have thousands of functions in a module but only want to exclude a few patterns. In this case, it becomes impractical trying to list all probe patterns except those few you want to exclude. One way to deal with this is to use [! to exclude certain characters. For example, if we construct the clause below, we can exclude function patterns with leading "xyz":
2007 Oct 02
0
patch: allow R CMD build exclude patterns to match symlinks
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.
2004 Jul 03
1
include/exclude patterns to copy just certain files?
I am attempting to copy only certain files down a directory tree. I know which files I want. I could generate a file of just those with 'find'. But having read the docs I have been trying to use the --include and --exclude patterns to have rsync pick the right files itself. But I can't figure it out. I am suspecting that I can't do what I want to do. Source example, this is
2015 Jun 09
0
Problem when excluding unreadable files via pattern and using --fake-super
Hey, I am experiencing a problem when excluding files that are not readable by the user on the source side. rsync version is 3.1.1. on debian jessy. Here is a "minimal" example: # preparation: $ mkdir -p source/subdir $ touch source/subdir/ignored_file $ sudo chown root:root source/subdir/ignored_file $ sudo chmod 600 source/subdir/ignored_file $ mkdir
2010 Jun 10
1
selecting and excluding files through a pattern
I have the following files list: > list.files() [1] "Prostate-Cancer_cvs_Dir" [2] "Prostate_Cancer-miRNAs&Genes.Pathway.xml" [3] "Prostate_Cancer_Pathways-miRNAs-GeneTargets-Dir" [4] "Prostate_Cancer_Pathways-miRNAs-GeneTargets-Dir.zip" [5] "Prostate-miRNAs.OrganTargets.txt"
2003 Feb 06
1
Trouble with include/exclude patterns
I'm using rsync 2.5.4 on my RedHat 7.3 client laptop and rsync 2.5.5 on my RedHat 8.0 server. On the client, I have a directory "rpm" with 5 subdirectories, out of which I only want to copy the one called SRPMS across. I also have another directory ".mozilla" out of which I want to copy across 2 files. I have constructed the following rsync invocation: rsync -e ssh -av