Displaying 20 results from an estimated 10000 matches similar to: "Rsync 2.6.8 released (incl. xattrs.diff security note)"
2006 Mar 11
0
Rsync 2.6.7 released
I have released rsync version 2.6.7.
You can read all about the latest improvements and bug-fixes that went
into this release on this page:
http://rsync.samba.org/ftp/rsync/NEWS
The tar file of the source and its signature are here:
http://rsync.samba.org/ftp/rsync/rsync-2.6.7.tar.gz
http://rsync.samba.org/ftp/rsync/rsync-2.6.7.tar.gz.asc
See the web site for other download
2006 Mar 11
0
Rsync 2.6.7 released
I have released rsync version 2.6.7.
You can read all about the latest improvements and bug-fixes that went
into this release on this page:
http://rsync.samba.org/ftp/rsync/NEWS
The tar file of the source and its signature are here:
http://rsync.samba.org/ftp/rsync/rsync-2.6.7.tar.gz
http://rsync.samba.org/ftp/rsync/rsync-2.6.7.tar.gz.asc
See the web site for other download
2006 Nov 01
2
unsuccessful configure with 2.6.8 and acls and extended attributes...
(FreeBSD 6.1-RELEASE)
tar xzvf rsync-2.6.8.tar.gz
cd rsync-2.6.8.tar.gz
patch < patches/acls.diff
patch < ./patches/xattrs.diff
./prepare-source
./configure --enable-acl-support --enable-xattr-support --disable-debug
--with-rsyncd-conf=/usr/local/etc/rsyncd.conf --bindir=/usr/local/bin
Couldn't be more simple. But...when I try to 'make' :
(snip)
gcc -I. -I. -g -O2
2009 Aug 22
2
--xattrs requires protocol 30 or higher error
Hi there,
We are using rsync 3.0.6 on two identical SLES 10.2 servers. The
destination server is running rsyncd. When I include the -X switch in the
rsync command from the source I get the following:
--xattrs requires protocol 30 or higher (negotiated 29).
rsync error: protocol incompatibility (code 2) at compat.c(205)
[sender=3.0.6]
Both rsync versions are 3.0.6 protocol version 30.
Any
2006 Jun 10
1
Two(?) bugs in the xattrs patch
I recently found a bug in the xattrs patch, where it would apply the
wrong xattrs to some files in a transfer. While looking at the code,
I think I found another one (it sure looks wrong, but I haven't
figured out how to demonstrate it yet). Anyway, here's the patch:
The first hunk fixes the apparent bug. The second hunk fixes the
demonstratable bug.
I haven't (yet) looked to see
2007 Oct 30
1
Rsync 3.0.0pre4 errors with ACLs and Xattrs between OSX and Linux
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
It's my understanding that as of 3.0 rsync supports OS X ACLs and
extended attributes, and that it should be possible to backup a tree
from an OS X system that contains files and folders with ACLs and
extended attributes to a Linux host filesystem that has both
"user_xattrs" and "acl" enabled on the destination file system.
2008 Mar 02
2
DO NOT REPLY [Bug 5298] New: xattrs and acls do not work well together along with fake-super, even worse on XFS
https://bugzilla.samba.org/show_bug.cgi?id=5298
Summary: xattrs and acls do not work well together along with
fake-super, even worse on XFS
Product: rsync
Version: 3.0.0
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
Component: core
AssignedTo:
2007 Nov 15
2
2.6.9 w/ acl, xattr, and fake-super support?
Hello,
As i cannot get 3.0.0pre5 to work in my environment (throwing crazy
errors which i've posted previously), i would like to revert to 2.6.9 .
Of course, the reason i tried to use v3 in the first place was for the
acl, xattr, and fake-super options - which, evidently, can be enabled
under 2.6.9, as per the following sources:
http://lists.samba.org/archive/rsync/2007-February/017218.html
2012 Dec 27
0
Suggestion: 'method' slot for expand.grid() (incl. diffs)
Dear expeRts,
The order in which the variables vary in expand.grid() is often unintuitive. I
would like to suggest a 'method' slot for expand.grid() which requires only very
little changes (100% backward compatible) and which allows one to control this
order. Please find attached diffs against R-devel.
Cheers,
Marius
### ./src/library/base/R/expand.grid.R
2007 Jul 03
1
xattrs with --link-dest inconsistancy
Hello.
On May 22, someone reported that xattrs don't work right with --link-dest
on rsync 3.0.0cvs:
http://lists.samba.org/archive/rsync/2007-May/017768.html
I've run into the same problem, but on Red Hat Enterprise Linux 5:
# rsync --version
rsync version 2.6.8 protocol version 29
Copyright (C) 1996-2006 by Andrew Tridgell, Wayne Davison, and others.
<http://rsync.samba.org/>
2006 Oct 14
0
Rsync 2.6.9pre2 released
I've just released rsync 2.6.9pre2. This version is mainly some fixes
and general cleanup that I made after getting to run the source through
IBM's code checker.
Please test this out and email the rsync mailing list with any
questions, comments, bug reports, etc. Thanks!
Here are direct links for the tar file and its signature:
2006 Oct 14
0
Rsync 2.6.9pre2 released
I've just released rsync 2.6.9pre2. This version is mainly some fixes
and general cleanup that I made after getting to run the source through
IBM's code checker.
Please test this out and email the rsync mailing list with any
questions, comments, bug reports, etc. Thanks!
Here are direct links for the tar file and its signature:
2007 Feb 05
1
rsync 3-cvs missing prereqs/deps on osx
hi,
as it's been awhile since my last attempts w/ v269, i'm building the
latest rsync3-svs on osx 10.4.8; looking to see what's evolved re:
acls & xattrs support on osx ...
@ build, i note complaint abt a missing yodl2man, which originates with YODL.
YODL, then requires icmake.
as neither is available on osx, it's src build time.
on building debian's icmake (already
2011 Jun 29
1
rsync fails to write write xattr user.rsync
Hi all,
I'm trying to setup rsync for backup purpose.
Both client and server (storage) are using rsync 3.0.7 delivered by
Debian Squeeze.
The client invokes rsync using ssh (as root):
Backup:
rsync --archive --delete --exclude-from=/etc/backup.excludes
--numeric-ids --relative --rsh=ssh / backup at example.com::backup/
Restore:
rsync --archive --delete --numeric-ids --relative --rsh=ssh
2018 Jan 23
2
[Bug 13241] New: A problem with test for xattrs transfer
https://bugzilla.samba.org/show_bug.cgi?id=13241
Bug ID: 13241
Summary: A problem with test for xattrs transfer
Product: rsync
Version: 3.1.2
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: core
Assignee: wayned at samba.org
Reporter:
2017 Nov 01
1
[Bug 13115] New: .yo sources incompatible with current yodl version
https://bugzilla.samba.org/show_bug.cgi?id=13115
Bug ID: 13115
Summary: .yo sources incompatible with current yodl version
Product: rsync
Version: 3.1.2
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5
Component: core
Assignee: wayned at samba.org
2007 Jun 30
2
checksum-xattr.diff [CVS update: rsync/patches]
On 6/30/07, Wayne Davison <wayned@samba.org> committed:
> Added Files:
> checksum-xattr.diff
> Log Message:
> A simple patch that lets rsync use cached checksum values stored in
> each file's extended attributes. A perl script is provided to create
> and update the values.
Wayne,
You should be aware of two drawbacks of caching checksums in xattrs:
First,
2006 Dec 16
2
Document the removal of the ACL compatibility mode
Wayne,
I noticed that you quietly removed the compatibility mode for sending
ACLs to rsyncs before 2.6.8 in revision 1.169 of acls.diff. It would
be good to document this in the man page. A metapatch to acls.diff
that revises the documentation in rsync.yo is attached; I didn't
regenerate rsync.1 because I don't have yodl 2 set up. Where did you
get the version of yodl 2 that you are
2003 Mar 03
1
csum-length documentation
I was startled to find that the --csum-length option is not
implemented even though it is documented in the manpage.
Not a good thing.
Here's a patch that removes the manpage entry. I'd much
rather not see this option and actually have the csum_length
be per-file dynamic. Either way this patch should be
applied at least until the code changes.
The patch also brings rsync.1 and
2006 May 03
2
Rsync error on client end: unexpected tag 3 [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(843) [sender]
Hi guys:
First post for me on this list.
THE PROBLEM
===========
I have several linux servers (ranging from Redhat 7.3 to FC3) that use Rsync (version 2.6.8 and 2.6.7, read on for reasons) to backup their data. A typical rsync backup script looks like this:
------------------------------------------------------------------------------------------
#!/bin/sh
RSYNC_PASSWORD=<PASSWORD>
rsync