Displaying 20 results from an estimated 300 matches similar to: "rsync-exclude.patch."
2004 Apr 09
3
include/exclude bug in rsync 2.6.0/2.6.1pre1
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 want to
transfer)".
However, --files-from does not help one implement the --rsync-exclude=FILE
2003 Jan 14
3
.rsync-/.rsync+ patch and --link-dest example
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
2002 Nov 11
0
Regular Expression support
I have added regular expression support using a POSIX implementation.
The patch (against 2.5.5) is attached.
The implementation is simple and follows the same mechanism that is
implemented for normal searches.
I added these command line arguments:
--rexclude=PATTERN exclude files matching regexp PATTERN
--rexclude-from=FILE exclude regexp patterns listed in FILE
--rinclude=PATTERN
2001 Sep 30
0
Exclude sets generated with -C
Hi guys,
I recently stumbled across what I think is an rsync bug. The problem
was I was trying to rsync from one CVS checkout, to another, and was
using rsync -Cavz to do the job. In this CVS module, there happens to
be two sub-directories with the names of "core" and "tags"
respectively, which were ignored, since these names matched the
default CVS ignore list.
When rsync
2004 Jan 27
1
Differentiating debug messages from both sides
Some of the debug messages that rsync outputs (when verbose >= 2) can
occur on both sides of the connection. This makes it hard to know which
program is saying what. Some debug messages deal with this by
outputting a "[PID]" string at the start of the message. Unfortunately,
the startup message that tells us which pid is which is only output when
verbose >= 3, so there's a
2003 Jun 24
2
[PATCH] Limit recursion depth
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hy folks,
everybody knows, that rsync eats up a lot of memory, when rsyncing
a lot of files.
To avoid this i run rsync on different parts of the directory-tree
(e.g. first ~muchofileuser/muchofilesdir1 then
~muchofileuser/muchofilesdir2 and so on) and it works fine for me.
So i tried to do this in a automatical way (e.g perl/shell/whatever
2004 Apr 22
1
rsync problems from flist.c change
On behalf of the development team of R (www.R-project.org), I would like
to report the following problem with recent versions of rsync.
First, some background info. The R Development Core Team uses CVS for
maintainins its source code archive. Additionally, there is a mechanism
for "mirroring" some important (so-called recommended) extension
packages from a CRAN (Comprehensive R
2004 Feb 02
1
[PATCH] --one-file-system and automounter
We use rsync in a Linux installation script. First, the root filesystem
of another machine on the network is cloned with "rsync -axzH", and then
a few files are updated to give the clone its own identity. This works
fine, but last week, the Postfix mailer daemon on a new machine refused
to start because some lock files had a link count of 2. It turned out
that rsync had created two
2002 Nov 04
4
making --exclude-from=- read from stdin
--- exclude.c.org 2002-11-04 04:17:05.000000000 +0100
+++ exclude.c 2002-11-04 04:21:13.000000000 +0100
@@ -219,8 +219,15 @@
int fatal, int include)
{
struct exclude_struct **list=list1;
- FILE *f = fopen(fname,"r");
+ FILE *f;
char line[MAXPATHLEN];
+
+ if( fname[0]=='-' &&
2011 Jan 20
5
DO NOT REPLY [Bug 7927] New: Rsync does not sync folders named "tags"
https://bugzilla.samba.org/show_bug.cgi?id=7927
Summary: Rsync does not sync folders named "tags"
Product: rsync
Version: 3.0.3
Platform: x86
OS/Version: Linux
Status: NEW
Severity: major
Priority: P3
Component: core
AssignedTo: wayned at samba.org
ReportedBy: bugzilla at
2007 Jul 14
1
DO NOT REPLY [Bug 4786] New: deletes files in parent directory when destination directory doesn't exist
https://bugzilla.samba.org/show_bug.cgi?id=4786
Summary: deletes files in parent directory when destination
directory doesn't exist
Product: rsync
Version: 2.6.9
Platform: Other
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
Component: core
AssignedTo:
2002 May 22
1
rsyncd listing of directories
I just took a look at the 2.5.5 codebase to see how easy it would be to
write a little driver script that downloads a big directory tree from an
rsync daemon the chunky way (get a list of a module's subdirectories and
do the transfer by subdirectory). The reason for doing this is obvious
when you have large directory trees, as is the case for many of us.
Unfortunately the way list_only is
2003 May 07
1
Bug report: "exclude from" in rsyncd.conf is not effective.
The attached script file gives all the relevant details - I hope -
please ask if you need any more information.
/Sam
Sam Sexton <mailto:sam.sexton@reuters.com>
Reuters Coventry
Automated Dealing Technologies
Phone: +44 24 7625 6562
Fax: +44 24 7655 5203
-------------------------------------------------------------- --
Visit our Internet site at
2007 Jul 13
1
Beginner needs a guide
Hi,
I'm trying to get rsync to use a list of directories and their contents to
to another drive on a Windows XP machine.
I tried the command
rsync -rDPt --delete
--include-from=c:\include_list.txt
--exclude-from=c:\exclude_list.txt
/cygdrive/d/source/ /cygdrive/e/backup
But the trouble is that no matter what I put in the include_list file it
always copies everything in source. I even
2006 Apr 19
1
Logging rsync transfers
Hello
I run rsync on a server and I backup our office PCs to it using cwRsync
on Windows PCs. The command I use to backup these PCs is:
rsync -vbalz --stats --backup-dir=/yesterday_backups/
--exclude-from="exclude_list.txt" --files-from="include_list.txt"
--rsh="ssh" . username@mydomain.com:/path/to/folder
On the server, I have the rsync service started at
2002 Aug 02
1
[patch] exclude-from stdin
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
2005 Jun 20
1
--exclude-from options
Hello,
I'm configuring rsync to use --exclude-from option however it doesnt work as
I want to.
I have a directory /source/ which contains additional directories a, b, c.
In addition /source/ directory contains some db.* files that I dont want to
backup. The tricky part is that subdirectories /source/a, /source/b and
/source/c can have their own db* files wich I do want to keep.
so how
2006 Feb 22
1
Include Exclude .. a canonical way
I'm wrestling with include/exclude rules and not finding a way to do
this:
Simplified command: rsync -avv --exclcude-from=rsync_exclude \
~/ /dest/
Backup ~/ including ~/.kde3.5/share/apps/konqueror/bookmarks.xml
but excluding everything else under ~/.kde3.5
Here are some of what hasn't worked in an EXCLUDE file.
+ /.kde3.5/share/apps/konqueror/bookmarks.xml
2011 Jul 09
0
Problem with --dry-run
Hi Gents,
I have written a backup script with rsync, which is working fine for a long
time. Now a problem has occured. which I am not able to solve by my own:
Before I am doing the backup I am checkig if there are any changes to backup
...
rsync --delete $RSYNC_EXCLUDE -avzne "$RSYNC_SSH" $RSYNC_SOURCE
$RSYNC_DESTINATION
But when I have created a path of new directories in
2003 Aug 24
1
readdir() and read() errors ignored
We've just been hit rather badly by a very nasty bug that can cause rsync
to silently discard files or fill them with zeroes. It happens when e.g.
opendir() succeeds but readdir() returns an error; rsync does not check
for an error from readdir() and so simply ignores the error (along with
any remaining files in the directory). No error is reported to the user,
who will then happily