https://bugzilla.samba.org/show_bug.cgi?id=2240
--- Additional Comments From [EMAIL PROTECTED] 2005-01-15 11:04 ---
Please explain why the following reversed list and the current first-match
algorithm don't accomplish the same thing as the last-match example you cited:
- dir2/dir22/
" rules). Hence one cannot
perform an arbitrary way to match the rules!
I prefer to think about the rules in a "last match" approach as
sub-terms of a left-associative mathematical expression (evaluated from
left to right) on sets where the used operators are "union" (+)
es to the initial "+" or "-" to change their
meaning without adding any new incompatibilities in the syntax of the
include/exclude files. I think I'll go ahead and add this to the code that sends
the name over the socket, as it does not interfere with backward compatibility
https://bugzilla.samba.org/show_bug.cgi?id=2240
Summary: Add last-match/short-circuit processing of
include/exclude
Product: rsync
Version: 2.6.3
Platform: All
URL: http://cvs.openpkg.org/getfile/openpkg
https://bugzilla.samba.org/show_bug.cgi?id=2240
--- Additional Comments From [EMAIL PROTECTED] 2005-01-13 07:48 ---
Created an attachment (id=887)
--> (https://bugzilla.samba.org/attachment.cgi?id=887&action=view)
rsync.patch.lastmatch
--
Configure bugmail: https://bugzilla.samba.
On Mon, Jan 10, 2005 at 10:28:54PM +0100, David E. Meier wrote:
> However, this leads me to the conclusion I need to run rsync separatly for
> any of the drives, right?
It all depends on how the souce and destination directories match up.
If the destination has a dir named "C" and "D" (in the same
tree.
>
> Rsync only deletes inside directories that it sends, so you'll need to
> send the whole .../C/ dir if you want rsync to delete subdirs inside it.
> If you only want to transfer some of the dirs inside .../C/, you'll need
> to use the --include/--exclude syntax to
file tree.
Rsync only deletes inside directories that it sends, so you'll need to
send the whole .../C/ dir if you want rsync to delete subdirs inside it.
If you only want to transfer some of the dirs inside .../C/, you'll need
to use the --include/--exclude syntax to limit which direct
Hello list,
I try to keep a list of directories/files on windows in sync with the ones
on a remote machine. Basically syncing works fine, however I am
stuck/confused with the various possiblities using include/exclude
options. Your help is very much appreciated. Here's the scenario:
Local s
Wayne Davison wrote:
> Bob Proulx wrote:
> > rsync -a --include '*/' --include '**/a1/foo' --exclude "*" . example.com:/tmp/
>
> Yes, that is the way to use include/exclude without first figuring
> out where all the foo files are. As you not
On Sat, Jul 03, 2004 at 05:25:05PM -0600, Bob Proulx wrote:
> rsync -a --include '*/' --include '**/a1/foo' --exclude "*" . example.com:/tmp/
Yes, that is the way to use include/exclude without first figuring
out where all the foo files are. As you noted that
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 i
Unusual
Significance (R.O.U.S.'s). Your explanation and the man page on the Samba
site make it clear that if a parent directory is excluded, then all of its
descendents are also excluded. The man page I'd been looking at pertained
to an older rsync version and was less explicit about how incl
On Thu, May 06, 2004 at 01:20:34PM -0500, Michael C. Davis wrote:
> I've narrowed it down to a test script for a representative case
> which, again, should be working but isn't.
You fell victim to one of the classic blunders! The most famous of
which is, "Never get involved in a land war in Asia.
Hi, I'm using rsync to move the contents of one drive to another as part of
upgrading from an old Linux installation to a newer one. I have a script
which uses includes and excludes to select what to keep and what to throw
away, but for some reason my include rule isn't triggering when I think it
On Sat, Apr 10, 2004 at 08:56:16PM +0200, John Bowman wrote:
> It's a question of precedence. Feel free to change the precedence of
> the "server" excludes.
That doesn't fix anything, it just switches around which lists have
the problem. Also, server excludes MUST be obeyed because we want the
mo
On Sat, Apr 10, 2004 at 03:05:15PM +0200, John Bowman wrote:
> If you decide later that you don't want foo.c, you can always tweak it
> locally using --rsync-exclude (which works recursively, similar to
> .htaccess files in Apache).
Not with the patch you supplied. If the server's rules included
gt; some potential mishaps. For instance, if a server has specified these
> include/exclude rules:
>
> + /foo.c
> - /*.c
>
> it was done that way to say "I'll let you copy foo.c, but no other .c
> files." Not to say, "You must take foo.c whether you want
of the exclude cleanup to fix
some potential mishaps. For instance, if a server has specified these
include/exclude rules:
+ /foo.c
- /*.c
it was done that way to say "I'll let you copy foo.c, but no other .c
files." Not to say, "You must take foo.c whether you want it or n
As mentioned on the rsync home page, the --files-from=FILE option in rsync
version 2.6.0 is a useful option that allows one to "specify a list of
files to transfer, and can be much more efficient than a recursive descent
using include/exclude statements (if you know in advance what files you
On Sun, Oct 26, 2003 at 12:09:23AM +0400, Dennis Chelukanov wrote:
> Hello rsync,
>
> I run Rsync as standalone server (--daemon). Here is my rsync.conf
> file
>
[snip]
> exclude *
> include *.mp3
>
> Then i run rsync :
>
> /etc > rsync rsync://[EMAIL PROTECTED]/mp3files/test/
>
Hello rsync,
I run Rsync as standalone server (--daemon). Here is my rsync.conf
file
use chroot = yes
max connections = 10
#syslog facility = local5
log = /var/log/rsyncd.log
[mp3files]
path = /home/guitar
comment = directory
read only = yes
list = no
secr
Wayne Davison wrote:
On Tue, Oct 07, 2003 at 11:38:43AM -0700, jw schultz wrote:
I'd say the paragraph needs an overhaul.
See how you like the appended patch.
..wayne..
I think this is definitely an improvement. I would also vote for an
addition to the include/exclude section
On Tue, Oct 07, 2003 at 01:06:52PM -0700, Wayne Davison wrote:
> On Tue, Oct 07, 2003 at 11:38:43AM -0700, jw schultz wrote:
> > I'd say the paragraph needs an overhaul.
>
> See how you like the appended patch.
Three small things. While you are updating it capitalise the
first word of the first
On Tue, Oct 07, 2003 at 11:38:43AM -0700, jw schultz wrote:
> I'd say the paragraph needs an overhaul.
See how you like the appended patch.
..wayne..
--- rsync.yo18 Aug 2003 23:52:43 - 1.127
+++ rsync.yo7 Oct 2003 20:03:14 -
@@ -132,12 +132,17 @@
quote(rsync -avz foo:src/b
On Tue, Oct 07, 2003 at 11:04:42AM -0700, Wayne Davison wrote:
> On Tue, Oct 07, 2003 at 10:45:13AM -0700, jw schultz wrote:
> > Also, it is incorrect. The trailing slash means the contents of the
> > directory (excluding .).
>
> Nope. The code specifically adds the '.' dir to the list of files
On Tue, Oct 07, 2003 at 10:45:13AM -0700, jw schultz wrote:
> Also, it is incorrect. The trailing slash means the contents of the
> directory (excluding .).
Nope. The code specifically adds the '.' dir to the list of files to
send, which is why the attributes get sent and why recursion occurs.
T
On Tue, Oct 07, 2003 at 10:21:16AM -0700, Wayne Davison wrote:
> On Tue, Oct 07, 2003 at 09:55:45AM -0700, jw schultz wrote:
> > This should probably be attached to this paragraph early in the USAGE
> > section:
>
> I've incorporated some suggested tweaks into the text you cited.
> See if you like
On Tue, Oct 07, 2003 at 09:55:45AM -0700, jw schultz wrote:
> This should probably be attached to this paragraph early in the USAGE
> section:
I've incorporated some suggested tweaks into the text you cited.
See if you like this:
a trailing slash on the source changes this behavior to transfer al
> go.
> >
> >
> Yes - I assumed that this was probably some side-effect of
> the current implementation - and it's not really so much of
> a problem, as long as it is documented behaviour, because it
> doesn't seem to me to be intuitive behaviour to joe
> bloggs.
x27;s not really so much of a problem, as long as it
is documented behaviour, because it doesn't seem to me to be intuitive
behaviour to joe bloggs... I'd just re-read the include/exclude portion
of the manual page before I started this operation yesterday, to make
sure I was clear on
Yes, it is not immediately obvious that when rsync is transferring a
path that ends in '/' that it is really transferring the "." directory.
Thus, this command:
rsync -av /some/path/ /another/spot/
... actually transfers "/some/path/." to "/another/spot/.", which
updates its permissions/owner
On Mon, Oct 06, 2003 at 05:41:45PM +0100, Tim Small wrote:
[redacted]
> Hi,
>
> Think I've found either a documentation bug, in rsync (or possibly a
> code bug), with the include/exclude feature. This occurs on (at least)
> 2.5.5 and 2.5.6
>
> First I created a
Hi,
Think I've found either a documentation bug, in rsync (or possibly a
code bug), with the include/exclude feature. This occurs on (at least)
2.5.5 and 2.5.6
First I created a file list of files that I wanted backed up
[EMAIL PROTECTED] root]# cat /tmp/sendmail-rpmverify-out
/etc/
Jason Williams wrote:
> Hello everyone.
>
> I have a question about using the include/exclude function for rsync.
> What I am trying to do is backup specific directories and their
> corresponding data, while at the same time, excluding other directories.
>
> Specifically, I
On Thu, Jun 26, 2003 at 12:07:42PM -0700, Jason Williams wrote:
> rsync -avn --include-file=/home/rsyncfile /backupstorage/D/ /home/rsyncbak
The most common failing is people not specifying the excludes relative
to the root of the transfer (it's not relative to the root of the file
system). Thus,
Hello everyone.
I have a question about using the include/exclude function for rsync.
What I am trying to do is backup specific directories and their
corresponding data, while at the same time, excluding other directories.
Specifically, I have a backup server with the follow setup
illa/arb dir.
>
> It would copy nothing from arb, surely?
>
> > I'd also suggest putting the lines into an include file so that the
> > command-line only needs an --include-from=file_name directive. The
> > lines would get +/- prefixes to tell it what
On Thu, Feb 06, 2003 at 01:58:28AM -, Max Bowsher wrote:
> It would copy nothing from arb, surely?
Sorry, I meant to say that it might copy more from .mozzilla than just
arb, but a re-edit ruined that thought.
> I don't think .mozilla was in rpm:
You're right, I missed that. Duh. Hopefully
rom arb, surely?
> I'd also suggest putting the lines into an include file so that the
> command-line only needs an --include-from=file_name directive. The
> lines would get +/- prefixes to tell it what to include/exclude:
I don't think .mozilla was in rpm:
+ /rpm/SR
tive. The
lines would get +/- prefixes to tell it what to include/exclude:
+ /rpm/SRPMS/
+ /rpm/.mozilla/
- /rpm/*
+ /rpm/.mozilla/arb/
- /rpm/.mozilla/*
+ /rpm/.mozilla/arb/kfgj0v2y.slt/
- /rpm/.mozilla/arb/*
+ /rpm/.mozilla/arb/kfgj0v2y.slt/bookmarks.html
+ /rpm/.mozilla/arb/kfgj0v2y.slt/pr
Anand Buddhdev wrote:
> 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
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 fi
On Tue, Jan 21, 2003 at 08:12:31PM +, Faheem Mitha wrote:
> What I mean is that --exclude
> "*.pdf" would exclude "*.PdF" and "*.pdF" as well.
You currently have to do this:
*.[Pp][Dd][Ff]
The fnmatch() function that rsync currently uses for its pattern
matching only has a case-folding o
Dear People,
A friend asks
*
For the rsync include/exclude options is there a way to make it
case insensitive?
What I mean is that --exclude
"*.pdf" would exclude "*.PdF" and "*.pdF" as well.
I am loo
On Tue, Dec 10, 2002 at 09:18:06AM -0500, marco wrote:
> I even tried this but it include the whole /var/ folder !
> I just want /var/lib/zope.
The solution is that after you include something that is too general,
you need to exclude what you don't want. Like this:
/etc
/var
- /*
/var/lib
- /va
This is why regular expression matching is 1000 times more powerful.
I submitted a patch a few months ago.
marco ([EMAIL PROTECTED]) wrote:
> Le Mon, 9 Dec 2002 21:22:48 -0800
> jw schultz <[EMAIL PROTECTED]> ?crivait :
>
> I found this on the FAQ-O-Matic from the rsync webite
>
> http://rsync.s
Le Mon, 9 Dec 2002 21:22:48 -0800
jw schultz <[EMAIL PROTECTED]> écrivait :
I found this on the FAQ-O-Matic from the rsync webite
http://rsync.samba.org/fom-serve/cache/164.html
I'm so agree...
Is it possible to make it true ?
thanks
--
marco
--
Clé PGP publique : https://iftbqp.mine.nu/marc
Le Mon, 9 Dec 2002 21:22:48 -0800
jw schultz <[EMAIL PROTECTED]> écrivait :
> You forgot to include /var/ and /var/lib/ so it never even
> sees /var/lib/zope/
I even tried this but it include the whole /var/ folder !
I just want /var/lib/zope.
--
marco
--
Clé PGP publique : https://iftbqp.mine.
On Tue, Dec 10, 2002 at 12:08:54AM -0500, marco wrote:
> Hi,
> I just subscribe to ask you a question about patterns in exclude-include
> files.
> I just want some folders to be rsynced to a remote machine.
> What I tried is :
> IncludeFile
> -
> /etc/
> /var/lib/zope/
> -
Hi,
I just subscribe to ask you a question about patterns in exclude-include
files.
I just want some folders to be rsynced to a remote machine.
What I tried is :
IncludeFile
-
/etc/
/var/lib/zope/
- /*
---
result of
$$ rsync -avvrn --delete --delete-exc
Carlos Molina <[EMAIL PROTECTED]> wrote:
> Nope, isn't works, because rsync only fetchs /etc directory.
> On the output, you could see that /home nad /var is excluded (I
> suppose that is excluded by /* pattern)
Blah. Your right. This will work:
+ /etc
+ /home
+ /home/cmolina
- /home/*
+ /var
+
Carlos Molina <[EMAIL PROTECTED]> wrote:
> + /etc
> + /home/cmolina
> + /var/log
> - - /*
Huh? "- -" ? Mistake again?
> rsync isn't include directories under /home and /var, because it
> exclude recursively on /*
Well sure, but it would have included dirs under /home/cmolina and
/var/log.
The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
|Carlos Molina <[EMAIL PROTECTED]> wrote:
|
|>-BEGIN PGP SIGNED MESSAGE-
|>Hash: SHA1
|>
|>Greetings.
|>
|>I'm trying to make some backups using rsync, but I have some questions
|>about it.
|>
|>First, on the receiving side, i make a test with
Carlos Molina <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Greetings.
>
> I'm trying to make some backups using rsync, but I have some questions
> about it.
>
> First, on the receiving side, i make a test with this line.
>
> rsync -vv -e ssh --recursive --includ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greetings.
I'm trying to make some backups using rsync, but I have some questions
about it.
First, on the receiving side, i make a test with this line.
rsync -vv -e ssh --recursive --include-from=include.txt
cmolina@www-01:/ /tmp/cmolina
On incl
On Thu, Mar 21, 2002 at 03:24:39PM -0600, Joe Rice wrote:
>
>
> Dave Dykstra([EMAIL PROTECTED])@Thu, Mar 21, 2002 at 10:17:46AM -0600:
> > Let me explain Wayne's answer a little further. The main thing you need to
> > understand is that the exclude algorithm is applied recursively so any time
>
Dave Dykstra([EMAIL PROTECTED])@Thu, Mar 21, 2002 at 10:17:46AM -0600:
> Let me explain Wayne's answer a little further. The main thing you need to
> understand is that the exclude algorithm is applied recursively so any time
> there's an exclude that matches a directory, rsync will not descend
On Tue, Mar 19, 2002 at 11:55:50AM -0800, Wayne Davison wrote:
> Seems to me that the simplest solution is to name the directory
> explicitly:
>
> rsync -a --include "*/" --include "*.tif" --exclude "*" /film/jonah /tmp/film
>
> To accomplish the same thing using includes, you could do this:
>
[EMAIL PROTECTED]([EMAIL PROTECTED])@Tue, Mar 19, 2002 at 12:53:44PM -0700:
> My mistake. I never use the patterns in my application, so i forgot one
> of the gotchas in the doc.
> From rsync.1:
> If you end an exclude list with --exclude '*', note that
> since the algorithm is
Seems to me that the simplest solution is to name the directory
explicitly:
rsync -a --include "*/" --include "*.tif" --exclude "*" /film/jonah /tmp/film
To accomplish the same thing using includes, you could do this:
rsync -a --include /jonah --include "/jonah/**/" --include "*.tif" \
++
Tim,
thanks for the help...but, it still isn't working.
any more ideas?
I have tried:
rsync -avv --include "/film/jonah/**/sourceimages/*.tif" --exclude "*"
/film /tmp
rsync -avv --include "/film/jonah/
;m planning on
> camping out overnight to get tickets to "Johah".
>
> Tim Conway
> [EMAIL PROTECTED]
> 303.682.4917
> Philips Semiconductor - Longmont TC
> 1880 Industrial Circle, Suite D
> Longmont, CO 80501
> Available via SameTime Connect within Philips, n9hmg on AIM
>
ips, n9hmg on AIM
perl -e 'print pack(,
19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970),
".\n" '
"There are some who call me Tim?"
Joe Rice <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
03/19/2002 07:55 AM
To: [EMAIL PROTECTED]
cc:
hi.
I know this is a big topic on the list, please forgive me.
rsync -avv --include "/film/jonah/**/sourceimages/*.tif" --exclude "*" /film /tmp
i'm trying to copy all *.tif 's that are in a */sourceimages/ directory
and that are only under /film/jonah.
i would like to copy the directory t
t;
> Hi!
>
> playing with --include, --exclude, and --exclude-from=file I found these
> not working:
>
> xcnlm00s:/etc/adsm/script # rsync -navx --include="*/" --exclude="*" -e
> ssh newsfeed:/
> receiving file list ... done
> wrote 29 bytes read 28
Hi!
playing with --include, --exclude, and --exclude-from=file I found these
not working:
xcnlm00s:/etc/adsm/script # rsync -navx --include="*/" --exclude="*" -e
ssh newsfeed:/
receiving file list ... done
wrote 29 bytes read 28605 bytes 3014.11 bytes/sec
total size i
On Fri, Nov 30, 2001 at 03:18:16PM -0700, [EMAIL PROTECTED] wrote:
> You're right. the order dependency actually lets you create very complex
> include/exclude rules. for each item, each --include and --exclude is
> evaluated in commandline order, until the item has either
You're right. the order dependency actually lets you create very complex
include/exclude rules. for each item, each --include and --exclude is
evaluated in commandline order, until the item has either passed all the
tests, and is thus included, or has been excluded, at which
It is finally working but I am not sure if I understand it right. It
seems to me that the order in which 'include' and 'exclude' exist in the
command line is making all the difference. Check out the following two
commands:
*** include is BEFORE exclude - Working fine ! ***
[admx:test] $ rsync -va
11/30/2001 09:09 AM
To: [EMAIL PROTECTED]
cc: (bcc: Tim Conway/LMT/SC/PHILIPS)
Subject:include/exclude ?
Classification:
All,
Could someone please help me resolve this:
[admx:test] $ ls
ERR01 ah01 ah02 an01 an02 mp01 mp02
[admx:tes
All,
Could someone please help me resolve this:
[admx:test] $ ls
ERR01 ah01 ah02 an01 an02 mp01 mp02
[admx:test] $ ls {an,mp,ERR}*
ERR01 an01 an02 mp01 mp02
I want to rsync only the "{an,mp,ERR}*" files across using the following
command but do not see the expected results.
On Thu, Nov 15, 2001 at 04:38:26PM -0800, Dave Madole wrote:
>
> I want to send a subset of directories sepcified in "include" arguments
> to a client, but I am creating all the
> peer and parent directories as well, although they are empty - here is
> basically what I'm doing.
>
> assuming I ha
I want to send a subset of directories sepcified in "include" arguments
to a client, but I am creating all the
peer and parent directories as well, although they are empty - here is
basically what I'm doing.
assuming I have /staging/upgrade/dir1, /staging/upgrade/dir2 and
/staging/upgrade/dir3 o
On Wed, Sep 26, 2001 at 09:17:03AM +0300, Coroiu Cosmin Marius wrote:
> Dave Dykstra wrote:
> >
> > On Tue, Sep 25, 2001 at 12:18:31PM +0300, Coroiu Cosmin Marius wrote:
> > > Hello all !
> > > I want to save some of the directories and files from my home dir.For
> > > that I
Dave Dykstra wrote:
>
> On Tue, Sep 25, 2001 at 12:18:31PM +0300, Coroiu Cosmin Marius wrote:
> > Hello all !
> > I want to save some of the directories and files from my home dir.For
> > that I create a new directory where I moved the file for sync and I made
> > some symlink
On Tue, Sep 25, 2001 at 12:18:31PM +0300, Coroiu Cosmin Marius wrote:
> Hello all !
> I want to save some of the directories and files from my home dir.For
> that I create a new directory where I moved the file for sync and I made
> some symlinks to the dirs which I want to inc
Hello all !
I want to save some of the directories and files from my home dir.For
that I create a new directory where I moved the file for sync and I made
some symlinks to the dirs which I want to include in sync.The hidden
directoris (like .netscape) are not included in sy
urements (using rsync 2.3.2 which
> had an include optimization that did something similar if there were no
> wildcards) to show what the performance impact would be.
>
> - Dave Dykstra
>
>
> Taking that message as a template, I created the following command to
> try to mo
ormance impact would be.
- Dave Dykstra
Taking that message as a template, I created the following command to
try to move two files:
rsync -vaR --include 'devel/a.html' --include 'devel/b.html' --include
'*/' --exclude '*'
somebox.foo.com::staging/Increm
On Wed, May 09, 2001 at 08:57:49AM -0400, [EMAIL PROTECTED] wrote:
>
> I read through the archives, and have gotten alot of leads, but still
> have not figured out the exact combination for what I am trying to do.
>
> I am copying individual machine's apache logs to a single machine to
> run log
I read through the archives, and have gotten alot of leads, but still
have not figured out the exact combination for what I am trying to do.
I am copying individual machine's apache logs to a single machine to
run log analysis on them. basically, what I have tried:
rsync -ra -v --include "/*/2
On Fri, Apr 06, 2001 at 02:40:43PM +1000, Greg Burley wrote:
> Harry Putnam wrote:
> > I want only binary-all/ binary-i386/ and disks-i386
> >
> > My command line looks like:
> > rsync -navvz --exclude-from=rsync_woody_exclude
> > rsync://ftp.debian.org/debian/dists/woody/ .
> >
> > I
At 04:20 PM 4/5/01 -0700, Harry Putnam wrote:
>I never heard of anonftpsync and really don't think I want to get into
>yet another confusing tool. I couldn't follow your tips and clues.
>What is actually happening there? You run two different syncing tools
>on the same stuff or what?
>
>The excl
Harry Putnam wrote:
> I want only binary-all/ binary-i386/ and disks-i386
>
> My command line looks like:
> rsync -navvz --exclude-from=rsync_woody_exclude
> rsync://ftp.debian.org/debian/dists/woody/ .
>
> I'm trying for a dryrun to see how my exclude rules work
>
> cat rsync_wood
Scott Sharpe <[EMAIL PROTECTED]> writes:
[...]
> ##
> TO=/home/ftp/pub/debian
> RSYNC_HOST=debian.uchicago.edu
> RSYNC_DIR=debian/
> EXCLUDE="--exclude *alpha.deb --exclude *m68k.deb --exclude \
[...]
>
> rsync -rltvz --delete \
> --ex
in the rsync man page. A workaround for you may be to exclude
> "**/foo/*.c", but that's not complete because the semantics of "**" is such
> that including it anywhere in a pattern means that all asterisks can cross
> slash boundaries. Thus, it will match baz/foo/oof/bar.c. As I said back
> then, the rsync include/exclude semantics & implementation needs to be
> completely redone.
In the meantime the man page should probably be changed, but it's bound to
be very difficult to explain. Anybody interested in taking a crack at it?
- Dave Dykstra
At 08:50 PM 4/4/01 -0700, you wrote:
>Once again I find myself in the throws of a major pain in the butt
>figuring out how to exclude the files under directories or at least
>the directories and the files.
>
>Apparently I don't use rsync in enough different circumstance for this
>to become routin
Once again I find myself in the throws of a major pain in the butt
figuring out how to exclude the files under directories or at least
the directories and the files.
Apparently I don't use rsync in enough different circumstance for this
to become routine.
Every single time I want to use rsync f
On Mon, Mar 19, 2001 at 03:39:39PM +1100, Andrew Tridgell wrote:
> > [60GB]
> > path = /home/ftp/pub
> > comment = Basic mirror. Maximum of 60GB in size.
> > include from = /etc/rsync.d/60gb.conf
> >
> > [90GB]
> > path = /home/ftp/pub
> > comment = Basic m
> [60GB]
> path = /home/ftp/pub
> comment = Basic mirror. Maximum of 60GB in size.
> include from = /etc/rsync.d/60gb.conf
>
> [90GB]
> path = /home/ftp/pub
> comment = Basic mirror. Maximum of 90GB in size.
> include from = /etc/rsync.d/90gb.conf
>
ns all the include / exclude
statements from the 60gb.conf file and the 90gb.conf file. In this manor
since rsync applys include / exclude statements on a first match basis I
could define something like this:
/etc/rsync.d/90gb.conf:
# Include all PPC code
+ /linux/PPC/
/etc/rsync.d/60gb.conf:
# includ
On Sat, Feb 10, 2001 at 08:30:32AM -0800, Harry Putnam wrote:
...
> > After looking thru the examples in man page it seems this command line
> > should do it:
> >
> > rsync -nav --include "*/" --exclude "alpha/" \
> >--exclude &
Harry Putnam <[EMAIL PROTECTED]> writes:
> Sorry, but I don't use rsync in enough situations to remember how to
> inovke the confusing rules for include/exclude.
>
> The man page makes a valient effort at giving direction but infact it
> is rather confusing still.
Sorry, but I don't use rsync in enough situations to remember how to
inovke the confusing rules for include/exclude.
The man page makes a valient effort at giving direction but infact it
is rather confusing still. And seems fairly complex.
Here is the current scene.
A server (r
101 - 195 of 195 matches
Mail list logo
