Displaying 20 results from an estimated 800 matches similar to: "Bug#306368: filter rules are too modern for remote rsync (which is 2.5.6)"
2007 Jul 20
0
[ycui1@bloomberg.com: Re: rsync bug?? (rsync fails when -C is used).]
On Thu, Jul 19, 2007 at 06:24:10PM -0400, Matt McCutchen wrote:
> The remote rsync is running out of memory as it collects the CVS
> ignore rules (add_rule). Something could be awry with the CVS ignore
> rules, or the machine could just be low on memory. Please run rsync
> again with -vvv (three verbose options), which will make the remote
> rsync show (among other useful
2007 Jul 19
2
rsync bug?? (rsync fails when -C is used).
hi, All.
I just compiled the latest rsync (2.6.9). but I'm getting an error when
I use the -C option.
eg:
$ rsync -aCv host1:/home/john/data/ /home/john/data
receiving file list ... ERROR: out of memory in add_rule [sender]
rsync error: error allocating core memory buffers (code 22) at util.c(115) [sender=2.6.9]
rsync: connection unexpectedly closed (8 bytes received so far) [receiver]
2011 Oct 28
3
Strange bug (buffer overflow) happening only under cron
Hi,
I am running OS X Snow Leopard on the 'sender' side and
Linux (2.6.32, possibly fedora but unsure) on the 'receiver'
side. Both with rsync 3.0.9.
If I run the following command from the command line:
/usr/local/bin/rsync -av -e "ssh -i \
/Users/pedrofortunyayuso/.ssh/backup_pfortuny_net" \
--filter ': rsync.dirs' ~/ pfortuny at
2010 Feb 05
1
Error 11: can not backup /var/lib/zope2.9
Moin,
I wrote a small backup script that use rsync: r5backup
(http://sourceforge.net/projects/r5backup/). It backup dozen of unix machines
for many people.
But when I try to backup /var/lib/zope2.9 I get an error 11. It does not
matter if zope is running or not.
I can't see an error meassge in the (verbose) logfile:
[client] parse_filter_file(/etc/r5backup/profiles/boulder.exclude,0,3)
2013 Mar 20
2
netfilter+libvirt=(smth got broken?)
Hello,
I'm having problem setting up filtering traffic for a virtual machine
managed by libvirt. Strange thing is, such a setup has been working fine
for me on an older version of distro (namely, opensuse 11.3 w/updates,
kernel 2.6.34, libvirt 0.8.8) but refused to work on shiny new opensuse
12.4 (kernel 3.7.10, libvirt 1.0.2).
The definition of filter in question is pretty simple:
2009 Aug 18
2
rsync 3.0.4 under cygwin: problems with --exclude
Hi all,
I'm trying to backup a disk using rsync but I need to exclude some folder.
I'm using rsync 3.0.4 under cygwin on a winxp machine.
The script that I use is:
# ---------------------------------------------------------------- #
SRCDIR=/cygdrive/d
LOGDIR=/cygdrive/f
BCKDIR=/cygdrive/f/Backup
rsync -auv --progress --delete --delete-excluded --log-file=$LOGDIR/`date
+%Y%m%d`.log
2004 Mar 25
1
Per-directory .cvsignore too aggressive
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
2005 Jan 31
1
[patch] add "--ignore" option
Hi,
The patch below adds a "--ignore" option to rsync, which means
"--exclude-but-dont-delete-even-if-we-specified--delete-excluded".
I need this for a few tasks, the simplest of which is to have rsync resist
trying to delete NetApp filers' ".snapshot" directories.
The change is fairly simple (the boolean filter returns become tri-state),
and works for me both
2004 Mar 24
1
incorrect exclude list with -C
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
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
2018 Jun 10
1
[Bug 13467] New: an xattr filter rule is treated as a file filter rule on the remote side
https://bugzilla.samba.org/show_bug.cgi?id=13467
Bug ID: 13467
Summary: an xattr filter rule is treated as a file filter rule
on the remote side
Product: rsync
Version: 3.1.3
Hardware: All
OS: All
Status: NEW
Severity: major
Priority: P5
Component: core
2018 Apr 29
3
bug: xattr filter rule treated as file filter rule on the remote side
Summary: an xattr filter rule (e.g. --filter='-x! user.*’, which is suggested by the documentation) is treated as a file filter rule on the remote side.
Repro #1, sender is local:
host1$ rsync --filter=‘-x! user.*' -avvvHX --delete /tmp/test/. host2:test
...
[Receiver] add_rule(-! user.*)
Repro #2, sender is remote:
host1$ rsync --filter=‘-x! user.*' -avvvHX --delete host2:test/.
2002 Jul 25
1
OpenSSH 3.4p1's top level .cvsignore file
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
2002 Jul 20
0
[Bug 366] New: .cvsignore shouldn't be in distrib
http://bugzilla.mindrot.org/show_bug.cgi?id=366
Summary: .cvsignore shouldn't be in distrib
Product: Portable OpenSSH
Version: -current
Platform: ix86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Build system
AssignedTo: openssh-unix-dev at mindrot.org
2004 Feb 08
2
strange behaviour with -C
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
2004 Apr 27
0
Merging excludes using ". FILE"
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
2003 Feb 16
1
rsync-exclude.patch.
> 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
2001 Apr 30
2
Add a couple .cvsignore files?
It would be nice if the CVS source had a .cvsignore file in the main
dir with the following items:
ssh scp sshd ssh-add ssh-keygen ssh-keyscan ssh-agent sftp-server sftp
configure config.h.in config.h config.status Makefile
ssh_prng_cmds *.out
Plus a .cvsignore file in openbsd-compat that ignored "Makefile".
..wayne..
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
2005 Sep 16
1
Bug#314473: rsync still fails badly with an "!" in .cvsignore
Here a bug report about "!" not working properly in 2.6.4 and above,
paraphrased...
> Ok, see attachment. I've tested it right now between two hosts
> running rsync 2.6.3-2 and 2.6.6-1. It works in the forward direction,
> backwards it gives
>
> '!' rule has trailing characters: !
> rsync error: syntax or usage error (code 1) at