> On Tue, Jan 24, 2023 at 11:51:42PM -0500, Roger wrote:
>I keep getting the following error. After several years I've had it, and am
>posting to the mailing list in hopes of better advice than stuckchange.
>
>rsync: [generator] failed to set times on "/mnt/tmp/.": Operation not
>permitted (1)
>
ir-times),
and this may or may not work. However, this exclusion tends to affect all
files and directories, and most times in my experience, maynot be a desireable
solution.
I've also tried an exclusion (and I thought this was crafty thinking on my
part), for omitting the top dir, "eg.
ut we do want these ones.
> >
> > so we want server:mirrors/foo/bar/*
> >
> > How do we place our rsync command?
> >
> > we have tried all kinds of --include=foo/bar/ --exclude=*
> > servername:mirrors/
> > we tried an include exclude include exclude too
ut bar also has
> dozens of directories - but we do want these ones.
>
> so we want server:mirrors/foo/bar/*
>
> How do we place our rsync command?
>
> we have tried all kinds of --include=foo/bar/ --exclude=*
> servername:mirrors/
> we tried an include
?
we have tried all kinds of --include=foo/bar/ --exclude=*
servername:mirrors/
we tried an include exclude include exclude too, infact every conceivable
method I've tried for hours, just about to give up with conclusion it can
not be done.with rsync but before I delete now outdated reposit
On Mon, Jan 24, 2022 at 1:08 AM Jürgen Bausa via rsync <
rsync@lists.samba.org> wrote:
> However, it didn't work in the beginning and took me some time to find
> out, that a space at the end (e.g. "+ /mnt/Windows/Users " in the second
> line) will be interpreted and thus, the directory is assumed
On Mon, Jan 24, 2022, Paul Slootman via rsync wrote:
>On Mon 24 Jan 2022, Jürgen Bausa via rsync wrote:
>>
>> However, that's just a proposal. But the behavior of trailing spaces is
>> something I guess should be corrected.
>
>Is it?
>How would you otherwise specify a space that you *do* intend t
On Mon 24 Jan 2022, Paul Slootman via rsync wrote:
>
>On Mon 24 Jan 2022, Jürgen Bausa via rsync wrote:
>>
>> However, that's just a proposal. But the behavior of trailing spaces is
>> something I guess should be corrected.
>
>Is it?
>How would you otherwise specify a space that you *do* intend t
On Mon 24 Jan 2022, Jürgen Bausa via rsync wrote:
>
> However, that's just a proposal. But the behavior of trailing spaces is
> something I guess should be corrected.
Is it?
How would you otherwise specify a space that you *do* intend to be
relevant?
Paul
--
Please use reply-all for most rep
I am running debian bullseye which comes with rsync 3.2.3. and was struggling
with writing a correct exclude-from file. I want to exclude everything under
/tmp and /mnt, but include everything under/mnt/Windows/Users/jba. This is what
I came up in the end and what works:
+ /mnt/Windows/Users
sions. Any advice?
rsync -aXvr --times --links
--exclude={'*.vdi','*.vmdk','*.ova','*.qcow2','.config/discord/'}
/home/path/ user@nas:/NAS/HOME/destination/
Are there supposed to be some kind of brackets around this?
Using these brackets with
On Mon 03 Aug 2020, Matt Stevens via rsync wrote:
> So I've gotten excluding paths to work as a standalone command. When I paste
> this into a script however, it ignores the exclusions. Any advice?
>
> rsync -aXvr --times --links
> --exclude={'*.vdi','*.vmdk&
So I've gotten excluding paths to work as a standalone command. When I
paste this into a script however, it ignores the exclusions. Any advice?
rsync -aXvr --times --links
--exclude={'*.vdi','*.vmdk','*.ova','*.qcow2','.config/discord/'}
Hi Matt,
On Sat, Aug 01, 2020 at 10:10:49PM -0400, Matt Stevens via rsync wrote:
> I lack development skills. Would there be a way for rsync to be passed an
> option to exclude a specific path during a sync operaton? All of my attempts
> to use exclude have failed, as it does not resp
on to exclude a specific path during a sync operaton? All of my
attempts to use exclude have failed, as it does not respect paths, only
filetypes.
--
Regards,
Matt Stevens
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options:
https://bugzilla.samba.org/show_bug.cgi?id=11909
Wayne Davison changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On Sat, Jul 11, 2020 at 12:59 AM Roland wrote:
> can "--filter" statements completely replace "--exclude" statements
Yes. The old-style exclude/include options just turn into the simplest
form of exclude/include filter rules.
..wayne..
--
Please use reply-all fo
Hello,
i have a backup script where i first used "--exclude-from" only. users
of my script can set exclude statements in backup client specific
property files.
later on, i needed to extend the script because of special requirement ,
so i needed to introduce usage of "--filter=&#x
https://bugzilla.samba.org/show_bug.cgi?id=14395
Bug ID: 14395
Summary: Add an option to remove exclude files from the source
Product: rsync
Version: 3.2.0
Hardware: All
OS: All
Status: NEW
Severity
https://bugzilla.samba.org/show_bug.cgi?id=14371
--- Comment #7 from Wayne Davison ---
If you don't want something deleted on the receiving side, you need to protect
it via either a protect rule or an exclude rule. Using --delete-excluded just
turns all exclude rules into hide rules,
https://bugzilla.samba.org/show_bug.cgi?id=14371
Wayne Davison changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
touch dest/file2
touch dest/file3
rsync -ri --delete-excluded -filter 'H file3' --exclude 'file2' src/ dest/
Note that only file2 exists in both directories initially, meanwhile file1
exists only in the source, and file3 exists only in the destination. I want
file1 to be tr
https://bugzilla.samba.org/show_bug.cgi?id=14371
--- Comment #5 from Haravikk ---
Oh, I see; so hide actually does what I need, you confused me with the mention
of not using --delete-excluded, as it actually seems to work just fine with a
mixture of hide and exclude rules for different items
https://bugzilla.samba.org/show_bug.cgi?id=14371
--- Comment #4 from Wayne Davison ---
You don't add an exclude rule, you add a hide rule. An exclude rule is a
combination of a hide (server side) and a protect (client side). So you choose
between the 3 idioms (hide, protect, exclude) depe
https://bugzilla.samba.org/show_bug.cgi?id=14371
--- Comment #3 from Haravikk ---
If I remove --delete-excluded then how do I ensure my backups remove items
matching new exclusion rules? For example, if I identify a new cache folder or
such that I don't want to copy, and it add to my exclusion ru
|RESOLVED
Resolution|--- |WONTFIX
Status|NEW |RESOLVED
--- Comment #1 from Wayne Davison ---
Just don't use --delete-excluded. For anything that you want to exclude on the
sending side without excluding it o
|RESOLVED
--- Comment #1 from Wayne Davison ---
Just don't use --delete-excluded. For anything that you want to exclude on the
sending side without excluding it on the receiving side you should use a "hide"
filter rule instead. This way you'll never have 2 rule
https://bugzilla.samba.org/show_bug.cgi?id=14371
Bug ID: 14371
Summary: Combined Exclude & Protect Filter Type
Product: rsync
Version: 3.2.0
Hardware: All
OS: All
Status: NEW
Severity: enhance
On Wed, Apr 8, 2020 at 8:15 AM Gerard E. Seibert wrote:
> Since this does not happen on all of the mirror sites, I would like a way
> to get a list or have rsync display the IP of the site it received an error
> message from and a way to block the use of that IP in the future. Is that
> possible?
FreeBSD 11.3 p7 /amd 64
rsync version 3.1.3 protocol version 31
Copyright (C) 1996-2018 by Andrew Tridgell, Wayne Davison, and others.
Web site: http://rsync.samba.org/
Capabilities:
64-bit files, 32-bit inums, 64-bit timestamps, 64-bit long ints,
socketpairs, hardlinks, symlinks, IPv6,
Either format is correct. However, there is no quoting or escaping in
the file. So:
- filename1
- file name 1
or without the -
On 1/3/20 1:45 PM, @lbutlr via rsync wrote:
> I have seen two main styles in examples for using rsync with exclude-from.
>
> The first is simply a list of
I have seen two main styles in examples for using rsync with exclude-from.
The first is simply a list of filename, one per line.
The second is a list of filenames, one per line, prefixed with either a - or a
+ to indicate exclude/include. Which is correct?
Also, none show the correct style
>You need to switch to filters where you have the additional options
>hide, show, risk, and protect. See the filter rules section of man rsync.
Thanks for the hint. Though I've been using rsync for years this part has
somehow escaped me. I've read up on the filters and they do what I
need. The d
You need to switch to filters where you have the additional options
hide, show, risk, and protect. See the filter rules section of man rsync.
On 12/4/18 8:36 AM, Fabian Cenedese via rsync wrote:
> Hello
>
> I'm looking for a way to exclude and delete some items but not delete
>
>> I'm looking for a way to exclude and delete some items but not delete
>> other items. Use case:
>>
>> I'm on Windows where there are folders like recycle.bin and system
>> volume information on every drive. I can exclude them while backing
>> up
Hi,
On 5/12/18 12:36 am, Fabian Cenedese via rsync wrote:
> I'm looking for a way to exclude and delete some items but not delete
> other items. Use case:
>
> I'm on Windows where there are folders like recycle.bin and system
> volume information on every drive. I can e
Hello
I'm looking for a way to exclude and delete some items but not delete
other items. Use case:
I'm on Windows where there are folders like recycle.bin and system
volume information on every drive. I can exclude them while backing
up my data drive. But I now also have other da
* isn't a shell glob in this case it is a simple pattern wildcard
meaning "anything".
On 01/24/2018 02:23 PM, Ken Chase via rsync wrote:
> not a bug, buy colour me confused:
>
> /tmp/foo$ mkdir a
> /tmp/foo$ touch a/foo
> /tmp/foo$ touch a/.baz
> /tmp/foo$ cd
not a bug, buy colour me confused:
/tmp/foo$ mkdir a
/tmp/foo$ touch a/foo
/tmp/foo$ touch a/.baz
/tmp/foo$ cd ..
/tmp$ rsync -avP --exclude=a/* foo bar
sending incremental file list
created directory bar
foo/
foo/a/
sent 71 bytes received 20 bytes 182.00 bytes/sec
total size is 0
https://bugzilla.samba.org/show_bug.cgi?id=12940
Bug ID: 12940
Summary: rsync: -C/--cvs-exclude does not ignore SCM ignore
files (patch)
Product: rsync
Version: 3.1.3
Hardware: All
OS: All
On Fri, Mar 3, 2017 at 7:48 AM, Ken Chase
wrote:
> I think both situations could benefit from a --resolve-cmd-line-links
> switch to resolve COMMAND LINE-SUPPLIED symlinks.
>
You can specify symlinks in a --relative path with a trailing slash-dot
(and use /./ infix notation to trim paths). For e
On Fri, Mar 3, 2017 at 4:41 AM, Steve Dondley wrote:
> However, if I add a --copy-links option to the command, it appears to
> override my "exclude" directive and the contents of the symlinked directory
> gets downloaded anyway.
>
The use of --copy-links doesn't do
2017 at 07:41:10AM -0500, Steve Dondley said:
> >A thousand greetings,
> >
> >I'm trying to rsync a directory from a server to my local machine that
> has
> >a symbolic link to a directory I don't want to download. I have an
> >"exclude"
Fri, Mar 03, 2017 at 07:41:10AM -0500, Steve Dondley said:
>A thousand greetings,
>
>I'm trying to rsync a directory from a server to my local machine that has
>a symbolic link to a directory I don't want to download. I have an
>"exclude" option to exclude
Ah, sorry, it links to somewhere outside the directory. Thanks.
/home/blah/dir/unwanted_symlinked_dir points to /home/blah/other_dir
On Fri, Mar 3, 2017 at 10:03 AM, Paul Slootman
wrote:
> On Fri 03 Mar 2017, Steve Dondley wrote:
>
> > The directory I'm trying to copy from is: /home/blah/dir
>
On Fri 03 Mar 2017, Steve Dondley wrote:
> The directory I'm trying to copy from is: /home/blah/dir
>
> The symlink is /home/blah/dir/unwanted_symlinked_dir
>
> On Fri, Mar 3, 2017 at 8:10 AM, Paul Slootman wrote:
>
> > You don't say explicitly, is the target of the symlink inside or
> > outsi
chine that
> has
> > a symbolic link to a directory I don't want to download. I have an
> > "exclude" option to exclude the symlink which works fine. However, if I
> add
> > a --copy-links option to the command, it appears to override my "exclude"
&g
On Fri 03 Mar 2017, Steve Dondley wrote:
> I'm trying to rsync a directory from a server to my local machine that has
> a symbolic link to a directory I don't want to download. I have an
> "exclude" option to exclude the symlink which works fine. However, if I add
&
A thousand greetings,
I'm trying to rsync a directory from a server to my local machine that has
a symbolic link to a directory I don't want to download. I have an
"exclude" option to exclude the symlink which works fine. However, if I add
a --copy-links option to the co
https://bugzilla.samba.org/show_bug.cgi?id=12378
--- Comment #6 from Kevin Korb ---
If you want to sync files newer than say 3 days ago that is what --files-from
is for...
cd /source
find . -mtime -3 -print | rsync -vai --files-from=- . /target
The primary purpose of --files-from is to give rsyn
https://bugzilla.samba.org/show_bug.cgi?id=12378
--- Comment #5 from Alessio ---
(In reply to Wayne Davison from comment #4)
Well if it's by design I will not go further. But for me it's a missing
"feature" because one has to prepare the list beforehand while rsync could do
the job "while it's t
|RESOLVED
--- Comment #4 from Wayne Davison ---
Command args (which includes names inside a files-from file) are never excluded
by an exclude directive. You told rsync to copy it, so it copies it. Excludes
only affect matching of files that rsync finds inside directories that you
told it to copy then it would be excluded. If you excluded
userName/.cache/winetricks/msls31/InstMsiW.exe then it would be excluded.
Exclude is not patern matched against parts of things you explicitly tell rsync
to copy...
kmk@dementia[1%]> cd /tmp
kmk@dementia[2%]> mkdir test
kmk@demen
https://bugzilla.samba.org/show_bug.cgi?id=12378
--- Comment #2 from Alessio ---
(In reply to Kevin Korb from comment #1)
Excuse me, but i don't get it, what's the difference between excluding
(matching) the pattern from a --files-from and a remote host?
debugging the rsync transfer from the r
https://bugzilla.samba.org/show_bug.cgi?id=12378
--- Comment #1 from Kevin Korb ---
It did not copy the directory you excluded it copied the files within that
directory that you explicitly told it to copy and created the appropriate
directories to allow that to happen.
IOW, .cache is not relativ
https://bugzilla.samba.org/show_bug.cgi?id=12378
Bug ID: 12378
Summary: why i cannot exclude dir/files if using option
"--files-from"
Product: rsync
Version: 3.1.2
Hardware: x64
OS: Linux
At 14:19 25.05.2016, N.J. van der Horn (Nico) wrote:
>Content-Transfer-Encoding: 8bit
>
>Hi Fabi,
>
> From the man-page, at the end of FILTER RULES:
>
>---
>Note also that the --filter, --include, and --exclude options take one
>rule/pattern each.
>To add multiple on
Hi Fabi,
From the man-page, at the end of FILTER RULES:
---
Note also that the --filter, --include, and --exclude options take one
rule/pattern each.
To add multiple ones, you can repeat the options on the command-line,
use the merge-file syntax of the --filter option, or the
--include-from
Hi
I'd like to have a list of excluded items that I can always use
and combine them with job-specific excludes (or generally filters).
Is it possible to use --exclude-from more than once? Do I have
to combine the exclude files into one and give this to rsync?
Is there another possibility
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
On Fri, Nov 20, 2015 at 06:43:12PM -0500, Kevin Korb wrote:
> If you use --exclude=pattern instead of --exclude patter those become
> more obvious. Also, you wouldn't have turned 'media' into an
> additional source parameter.
You're right. Thanks.
--
Bob Holtzman
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If you use --exclude=pattern instead of --exclude patter those become
more obvious. Also, you wouldn't have turned 'media' into an
additional source parameter.
On 11/20/2015 06:33 PM, Bob Holtzman wrote:
> On Wed, Nov 18, 2015 a
On Wed, Nov 18, 2015 at 07:22:12PM -0500, Kevin Korb wrote:
> Note the lack of a space here: --exclude '/tmp'--exclude
>
> Also, just use / for the source instead of /.
>
> Also, don't use -z on a local copy.
Many thanks for the reply/solution. I've looked at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Note the lack of a space here: --exclude '/tmp'--exclude
Also, just use / for the source instead of /.
Also, don't use -z on a local copy.
On 11/18/2015 06:19 PM, Bob Holtzman wrote:
> Running debian wheezy w/ rsync 3.0.9-4. The c
Running debian wheezy w/ rsync 3.0.9-4. The command in question is
rsync -vahHz --delete --exclude '/proc' --exclude '*.iso' --exclude
'/home/holtzm/mail/backup' --exclude '/sys ' --exclude '/tmp'--exclude
'/media' /. /media/cf
> I investigated the rsync code and found the reason why.
> For every file in the source, it searches the entire filter-list looking
> to see if that filename is on the exclude/include list.** Most aren't, so
> it compares (350K - 72K) * 72K names (the non-listed files) p
I investigated the rsync code and found the reason why.
For every file in the source, it searches the entire filter-list looking to
see if that filename is on the exclude/include list. Most aren't, so it
compares (350K - 72K) * 72K names (the non-listed files) plus (72K * 72K/2)
names (the
I have a sensor collector system (very low-powered slow ARM cpu), and
another system which daily pulls the data files from it for processing.
There are about 1000 new files each day. As part of the processing it
decides that certain of the files are of no interest, and adds them to an
exclude
https://bugzilla.samba.org/show_bug.cgi?id=11253
--- Comment #2 from Vegard Nossum ---
(In reply to Wayne Davison from comment #1)
Thank you for the explanation.
--
You are receiving this mail because:
You are the QA Contact for the bug.
--
Please use reply-all for most replies to avoid omitt
|RESOLVED
--- Comment #1 from Wayne Davison ---
Excludes don't affect args, just items that are found in recursion. A
files-from list is the same as specifying all the names as args on the
command-line, and thus are not affected. Specifying an exclude of just the dir
name ma
https://bugzilla.samba.org/show_bug.cgi?id=11253
Bug ID: 11253
Summary: --exclude=dir doesn't work with --files-from=
Product: rsync
Version: 3.1.1
Hardware: All
OS: All
Status: NEW
Severity: n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- - #filename
On 04/12/2015 05:06 PM, Harry Putnam wrote:
> Can anyone tell me how to exclude a file that begins or ends with
> an octothorp (`#')?
>
> Something like #file or file#
>
> But not fi#le
>
> I'
Can anyone tell me how to exclude a file that begins or ends with an
octothorp (`#')?
Something like #file or file#
But not fi#le
I've tried these in an exclude file:
"#"*
*"#"
\#*
*\#
All seem to just be ignored
--
Please use reply-all for most replies to a
Hi
On Sat, 28 Feb 2015 06:41:59 +0300 Дугин Сергей wrote:
> rsync -a --exclude="tmp/*" /home/ /backup/home/
> If the folder /home/tmp/ is many millions of files, rsync
> think of this folder can be seen through the lsof -p PID
Or strace yes. It seems that rsync does an
On Sat 28 Feb 2015, ? ?? wrote:
>
> rsync version 3.0.9 protocol version 30
>
> rsync -a --exclude="tmp/*" /home/ /backup/home/
>
> It is necessary that the contents of the folder tmp copy, but the folder tmp
> in
> backup was created.
>
> I
Hi, Rsync.
rsync version 3.0.9 protocol version 30
rsync -a --exclude="tmp/*" /home/ /backup/home/
It is necessary that the contents of the folder tmp copy, but the folder tmp in
backup was created.
If the folder /home/tmp/ is many millions of files, rsync
think of this folder c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- --exclude not -exclude
- -exclude == -e -x -c -l -u -d -e which all happen to be valid.
On 08/22/2014 03:37 PM, Geoffrey Leach wrote:
> I've tried all of the permutations of exclude I can think of, so
> presumably I have some
I've tried all of the permutations of exclude I can think of, so presumably I
have some fundamental misunderstanding. The goal here is to exclude the file
tv11.html in the ftp directory.
rsync -a -n --verbose --one-file-system -exclude='ftp/tv1.html'
/usr/local/src /Media
dfc32 Mon Sep 17 00:00:00 2001
From: Karl-Philipp Richter
Date: Wed, 11 Jun 2014 00:27:30 +0200
Subject: [PATCH 2/2] added hint about distinction between shell and
exclude/include patterns to avoid users e.g. trying *rsync -a remote.com:*.c
/local/target/*
---
rsync.yo | 6 +-
1 file chang
https://bugzilla.samba.org/show_bug.cgi?id=10638
Summary: Add include/exclude files by mime type
Product: rsync
Version: 3.1.1
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P5
I'm syncing a download directory, where various programs drop their files. I
would like to exclude partial firefox downloads.
This could be accomplished by excluding "foo" and "foo.part", iff "foo.part"
exists. How can I accomplish this with exclude rules? Or
On 7 Aug, 2013, at 19:35 , AZ 9901 wrote:
>
>
> Le 7 août 2013 à 09:00, Mirek Lauš a écrit :
>
>>>
>>>> Le 11 juil. 2013 à 15:37, Mirek Lauš a écrit :
>>>>
>>>>> Hi,
>>>>>
>>>>> I'm facing
Le 7 août 2013 à 09:00, Mirek Lauš a écrit :
>>
>>> Le 11 juil. 2013 à 15:37, Mirek Lauš a écrit :
>>>
>>>> Hi,
>>>>
>>>> I'm facing problems with rsync using very large exclude-from list (around
>>>> 780k
>
>> Le 11 juil. 2013 à 15:37, Mirek Lauš a écrit :
>>
>>> Hi,
>>>
>>> I'm facing problems with rsync using very large exclude-from list (around
>>> 780k lines,
>>> 32MB in size). Clients reads whole exclude list, then the sende
I tried to increase the timeout but no luck.
Well, if the timeout came into play, wouldn't it just quit and tell that the
timeout was reached?
In my situation, client reads whole exclude list (about 78 rules), the
sender side starts to
receive the exclude rules, but just hangs at
Le 11 juil. 2013 à 15:37, Mirek Lauš a écrit :
> Hi,
>
> I'm facing problems with rsync using very large exclude-from list (around
> 780k lines,
> 32MB in size). Clients reads whole exclude list, then the sender receives the
> exclude
> rules but is stuck at around
Hi,
I'm facing problems with rsync using very large exclude-from list (around 780k
lines,
32MB in size). Clients reads whole exclude list, then the sender receives the
exclude
rules but is stuck at around line 32k ... Can you point me what to look out?
What information would be useful to
>> On Linux, an rsync command and exclude_file contents of:
>>
>> # cat exclude_file
>> /etc/alsa
>> # rsync -a --delete --delete-excluded --exclude-from=exclude_file /etc
>> server::module
>>
>> properly excludes /etc/alsa but not any file
On Mon 27 May 2013, Joseph L. Casale wrote:
> On Linux, an rsync command and exclude_file contents of:
>
> # cat exclude_file
> /etc/alsa
> # rsync -a --delete --delete-excluded --exclude-from=exclude_file /etc
> server::module
>
> properly excludes /etc/alsa but no
On Linux, an rsync command and exclude_file contents of:
# cat exclude_file
/etc/alsa
# rsync -a --delete --delete-excluded --exclude-from=exclude_file /etc
server::module
properly excludes /etc/alsa but not any file within /etc's directories that is
named alsa.
On Windows I don't
On 5/16/2013 2:38 AM, Paul Slootman wrote:
On Wed 15 May 2013, Brian K. White wrote:
I did in the case when it was only one pattern, but that was just a
simplified example.
The actual job involves too many include and exclude patterns to use
--include & --exclude, or even --include-from
On Wed 15 May 2013, Brian K. White wrote:
> I did in the case when it was only one pattern, but that was just a
> simplified example.
>
> The actual job involves too many include and exclude patterns to use
> --include & --exclude, or even --include-from and --exclude-
sing -f to specify a filter
rule to tell rsync to merge in a file with additional filter rules,
which is a bit of a roundabout way. Why not tell rsync directly to read
a file with include/exclude rules by using --exclude-from
I did in the case when it was only one pattern, but that was just a
s
using -f to specify a filter
rule to tell rsync to merge in a file with additional filter rules,
which is a bit of a roundabout way. Why not tell rsync directly to read
a file with include/exclude rules by using --exclude-from
Paul
--
Please use reply-all for most replies to avoid omitting the mailin
On 5/15/2013 5:17 AM, Paul Slootman wrote:
On Wed 15 May 2013, Brian K. White wrote:
Consider the following directory structure
/foo/aaa/*/*
/foo/bbb/*/*
/foo/ccc/*/*
I want to sync all of /foo,
but exclude /foo/aaa
rsync -avz /foo ${DEST}::root
Firstly, I always recommend that with
On Wed 15 May 2013, Brian K. White wrote:
> Consider the following directory structure
>
> /foo/aaa/*/*
> /foo/bbb/*/*
> /foo/ccc/*/*
>
> I want to sync all of /foo,
> but exclude /foo/aaa
> rsync -avz /foo ${DEST}::root
Firstly, I always recommend that with di
On 5/15/2013 4:13 AM, Brian K. White wrote:
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 oc
On 15.05.2013 04:13, Brian K. White wrote:
> How can I get it to exclude just the top-level directory "/foo/aaa" ?
With a '/' at the beginning you pin the pattern to the beginning.
You don't use "/" at the end of directory names, so i'm not sure if t
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/
Hi.
On Mon, 11 Mar 2013 23:17:06 +0100 Mark Casey wrote:
> On 3/11/2013 4:18 PM, Mark Casey wrote:
...
>> rsync -nav --no-t --numeric-ids --relative --include='*/' --exclude='*' \
>> /media/mnt/files /media/backups/mnt/
...
> I was wrong. The command
1 - 100 of 932 matches
Mail list logo
