--xattrs requires protocol 30 or higher error

2009-08-22 Thread Kirk Maule
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

Re: Include a directory inside an excluded one?

2009-08-22 Thread Wayne Davison
On Thu, Aug 20, 2009 at 08:41:40PM +0200, Nicolas KOWALSKI wrote: My problem is that I would like to synchronize a directory located inside /Ma musique/, the one named /Ma musique/iTunes/. As you noticed, rsync will not synchronize anything whose parent dir gets excluded. To fix this, stop

Re: --xattrs requires protocol 30 or higher error

2009-08-22 Thread Wayne Davison
On Sat, Aug 22, 2009 at 11:22:40AM +0100, Kirk Maule wrote: Both rsync versions are 3.0.6 protocol version 30. You'll undoubtedly find that there is an older rsync on the $PATH on one of the machines. e.g, try this: ssh hostname rsync --version Either get rid of the old version, or specify

Re: Differenc in exclude v 2.6.9 and v 3.0.4

2009-08-22 Thread Wayne Davison
On Thu, Jul 09, 2009 at 12:42:47AM -0500, Harry Putnam wrote: Is this actually a difference that was one way in an earlier (2.6.9) version and is different in the later (3.0.4) version? That seems unlikely to me... Yes, very unlikely. The combination of the options --include=Temp/**/ and

Re: partial-dir not being used?!

2009-08-22 Thread Wayne Davison
On Fri, Jul 17, 2009 at 02:13:00AM -0300, Carlos Carvalho wrote: There can be several partials in the partial dir for the same file, resulting from more than one interruption. No, there is only one partial file. Don't confuse a partial file with a temp file, which are different things in

DO NOT REPLY [Bug 6569] chmod-temp-dir fails on QNX

2009-08-22 Thread samba-bugs
https://bugzilla.samba.org/show_bug.cgi?id=6569 way...@samba.org changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

RFE: Xattr/super-user emulation?

2009-08-22 Thread Linda A. Walsh
I was just thinking -- would it be possible to just 'emulate' xattrs on systems that don't support them natively with a --Xe switch -- that would store the xattrs in a file .filename.xattr in the same dir as the copied file. The switch only be paid attention to on systems that don't support

RE: --xattrs requires protocol 30 or higher error

2009-08-22 Thread Kirk Maule
Good call. I observed rsyncd 2.6.8 starting up in the /var/log/rsyncd.log. Should the rsync*.tar.gz install procedure replaced rsyncd 2.6.8 as well as rsync 2.6.8 with the 3.0.6 version? Stopped the rscyncd and re-ran the install of the tar.gz but no change. The install was done as root.

Re: partial-dir not being used?!

2009-08-22 Thread Carlos Carvalho
Wayne Davison (way...@samba.org) wrote on 22 August 2009 09:15: On Fri, Jul 17, 2009 at 02:13:00AM -0300, Carlos Carvalho wrote: There can be several partials in the partial dir for the same file, resulting from more than one interruption. No, there is only one partial file. Don't confuse

Re: --xattrs requires protocol 30 or higher error

2009-08-22 Thread Wayne Davison
On Sat, Aug 22, 2009 at 08:49:10PM +0100, Kirk Maule wrote: Should the rsync*.tar.gz install procedure replaced rsyncd 2.6.8 as well as rsync 2.6.8 with the 3.0.6 version? Depends on how the package was built. Rsync is just one executable, so be sure to put it in a consistent spot. For your

[SCM] The rsync repository. branch, master, updated. v3.0.3-213-gce827c3

2009-08-22 Thread Rsync CVS commit messages
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project The rsync repository.. The branch, master has been updated via ce827c3e50cd168027a555ec961b6636e5b63e59 (commit) from

[SCM] The rsync repository. branch, master, updated. v3.0.3-214-g8a21be1

2009-08-22 Thread Rsync CVS commit messages
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project The rsync repository.. The branch, master has been updated via 8a21be11f08dca35e8db1bf7225975f90d66c997 (commit) from