similar to: Support for CACHEDIR.TAG excludes?

Hi rsync'ers, I'm soliciting feedback, discussion, and hopefully eventually support for a (currently very short and simple) proposal that would make it easier and more automatic for users to exclude from backups and other data transfers all the cache directories that various applications create and manage, such as Mozilla's web cache. The idea is simple: if applications that

Hello, Since the very first day I've been using rsync - some 15 years ago - the filtering rules caused great grieve. Their behaviour is just not the way I'd expect it be be and as I read the manpage. Usually I end up with some hand-written recipes, carefully documented,y including all the gotchas. This time however I failed and I see no other way than to ask for advice. Given the

As I alluded to in an earlier email on the subject of excludes, I had the idea of allowing a merge idiom (think "#include" in C) inside rsync's current exclude/include system. The idea is simple -- use the prefix ". " (dot space) in front of a filename, and that file will be incorporated into the contents of the current exclude/include rule(s). As a further feature, if the

Temporary images can be quite big, more than the space available in $TMPDIR when it's on a tmpfs; hence, place them in our cachedir instead. --- builder/builder.ml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/builder/builder.ml b/builder/builder.ml index 957bc37..3750e5f 100644 --- a/builder/builder.ml +++ b/builder/builder.ml @@ -378,6 +378,8 @@ let main () =

On Tue, Jan 23, 2018 at 06:01:08AM +0000, Ryan Lindsay wrote: > Hi Richard > > I have been playing around with your lovely libguestfs tools . I have however run into a bit of a problem > > Basically I have a 5.4T qcow2 virtual disk, which I made too small (bugger) > > So I had read that you can expand these with your virt-resize tools. > > So I tried this sort of

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

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

> 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

Hi! I'm just now preparing the first, still very experimental (way pre-1.0) release of a new archival tool, similar to (and based on) zip/unzip, with the difference that the enhanced zip tool can store x86-based decompressor code fragments in archives along with the compressed data, which the unzip tool runs in an isolated user-mode virtual machine in order to extract the data. The main

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

--- builder/cache.ml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/builder/cache.ml b/builder/cache.ml index 9e69bc1..86ac41b 100644 --- a/builder/cache.ml +++ b/builder/cache.ml @@ -35,7 +35,7 @@ type t = { let create ~verbose ~directory = if not (is_directory directory) then - mkdir directory 0o755; + mkdir_p directory 0o755; { verbose = verbose;

Hi, doing a rather usual backup: | rsync -av --delete /path/to/sender/ /path/to/receiver/ some items might be removed or overwritten on the receiving side. I'd like to keep a copy of these files/links/whatever. Is there a way to create a copy of them in another tree right before they are purged? Christoph

I received the following bug report for the Debian rsync package today. I wouldn't have expected 2.6.4 to refuse to talk to even a 2.6.2 in this way... Perhaps Wayne could comment? Paul Slootman On Tue 26 Apr 2005, Alexey Feldgendler wrote: > > Rsync fails to push filters to the the remote host if the remote rsync > is older than the Debian's. I've tried to connect to a

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

I have noticed that the contents of per-directory .cvsignore files apply outside their subtrees when using --cvs-exclude in rsync 2.6.0. In the results below, notice how dir1/.cvsignore is applying to a file in dir2. There is no ~/.cvsignore, and the CVSIGNORE variable is unset. % ls -AFR .: dir1/ dir2/ ./dir1: .cvsignore file1 ./dir2: file2.foo % cat dir1/.cvsignore *.foo % /usr/bin/rsync

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

This is largely code motion. --- src/appliance.c | 40 +++++++----------------------------- src/guestfs-internal.h | 1 + src/tmpdirs.c | 55 ++++++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 63 insertions(+), 33 deletions(-) diff --git a/src/appliance.c b/src/appliance.c index 2cf6374..d293c2b 100644 --- a/src/appliance.c +++ b/src/appliance.c @@ -48,7 +48,7

I posted previously about problems with X11() on my MAC using R 2.8.1 . After installing the securilty update for Tiger this morning, X11() now works from an xterm :-) However, I receive the following warnings with any plotting command using the default X11 settings. Fontconfig warning: no <cachedir> elements found. Check configuration. Fontconfig warning: adding

Rename the cache files like ‘qemu.stat’ etc so they include the qemu binary "key" (ie. size and mtime) in the name. This allows a single user to use multiple qemu binaries in parallel without conflicts. --- lib/qemu.c | 29 ++++++++++++++++++++++++----- 1 file changed, 24 insertions(+), 5 deletions(-) diff --git a/lib/qemu.c b/lib/qemu.c index 097d56929..1549bb33a 100644 ---

anyone who can help me understand- one of my developers reimported openssh snapshot from 0722 into cvs. he sent me the following email about an error he believes is in the snapshot i'm not a cvs-knowledgeable person, so i'm not all that clear on this, but should *.in files be in .cvsignore? i tried checking a later snapshot, but 0722 seems to be the latest one. .cvsignore is dated jun