similar to: .rsync-/.rsync+ patch and --link-dest example

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

> I like the idea of your rsync-exclude.patch and have thought > about hacking it in myself. However as you already have done the work > may I make a small suggestion...... can the name of the exclude file > (your .rsync) be specified in the flags.... e.g. > > rsync --rsync-exclude=.snapshot -axvH /here /there > > In this way different invocations (e.g. system and

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

> Just curious: what about the rsync+ patch? Thanks for the reminder. I've just committed Jos's rsync+ patch onto the "branch_mbp_rsyncplus_merge" branch. If it works OK and nobody screams I will move it across onto the main tree tomorrow or Wednesday. I see the patch doesn't add documentation about the new options to the man page, so we should fix that in the future.

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

-----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

I just received this bug report on Debian's rsync package. I've verified it. The entry from the manpage: -C [...] Finally, any file is ignored if it is in the same directory as a .cvsignore file and matches one of the patterns listed therein. Here the patterns of a .cvsignore file is apparently used to exclude file outside the directory where the .cvsignore file is found. Any

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

Hi! This problem gave me quite a headache tonight... I more or less have this source directory: hop@krautesel:/var/tmp$ ls -laR from/ from/: total 12 drwxrwxr-x 3 hop hop 4096 Feb 8 03:34 . drwxrwxrwt 6 root root 4096 Feb 8 03:34 .. drwxrwxr-x 2 hop hop 4096 Feb 8 03:18 CVS -rw-rw-r-- 1 hop hop 0 Feb 8

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

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

I am having trouble with rsync when I am trying to synchronize a Windows NT volume mounted with smb_fs (FreeBSD) and a unix volume which is also exported with Samba. There are instances where the DOS short name on the NT volume ends up as upper case and then doesn't match filenames which are used in the unix volumes which have been exported by Samba. I don't know if this is a Samba

--- 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]=='-' &&

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

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

https://bugzilla.samba.org/show_bug.cgi?id=2240 ------- Additional Comments From rse@engelschall.com 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.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the

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

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

rsync+ is ready to go onto HEAD. Could Jos or somebody else who's used the feature before please prepare a few paragraphs for the manpage explaining how they work? Either send a patch to the .yo files or just plain text. Thanks, -- Martin

Hi everybody! Now that RSYNC has RSYNC+ included a good usage would be to use RSYNC+ to gather update-date, then multicast that on your hosts and process it. So my question is: does anyone know of a product which does reliable multicasting? (source available would be preferred) Simple pointers are appreciated; if noone has one I'm thinking about writing one myself. Thanks for all help!