On 7/18/07, kimry <[EMAIL PROTECTED]> wrote:
###
patch -p1 < rsync-acl-patch
(Stripping trailing CRs from patch.)
patching file flist.c
patch unexpectedly ends in middle of line ===>> is that ok?
I think you are just missing the newline at the very end of
rs
##
patch -p1 < rsync-acl-patch {
http://lists.samba.org/archive/rsync/2006-November/016706.html}
(Stripping trailing CRs from patch.)
patching file flist.c
patch unexpectedly ends in middle of line ===>> is that ok?
Hunk #2 succeeded at 1003 with fuzz 1.
##
--
__
On 7/18/07, kimry <[EMAIL PROTECTED]> wrote:
I just started to use rsync-acl-2.6.9.tar.bz2
And I got the same error
Internal error: wrong write used in receiver.
Is there a fix for that?
The patch is here:
http://lists.samba.org/archive/rsync/2006-November/016706.html
Matt
Hi,
I just started to use rsync-acl-2.6.9.tar.bz2
And I got the same error
Internal error: wrong write used in receiver.
rsync error: protocol incompatibility (code 2) at io.c(1204) [generator=
2.6.9]
rsync error: received SIGUSR1 (code 19) at main.c(1182) [receiver=2.6.9]
it runs just
On Fri, Nov 10, 2006 at 07:16:43AM -0800, Wayne Davison wrote:
> Looks like the ACLs patch didn't get tested with --delete + --acls.
The xattrs patch has the same problem. If someone is using xattrs.diff
(which requires acls.diff too), the attached patch fixes both the ACL
code and the xattrs cod
On Fri, Nov 10, 2006 at 02:15:22PM +0100, Sven Strickroth wrote:
> [generator] make_file(home/administ,*,2)
> Internal error: wrong write used in receiver.
Looks like the ACLs patch didn't get tested with --delete + --acls.
Applying the attached patch will fix this.
..wayne..
---
Hi,
I'm using 2.6.9 but I get:
recv_files phase=1
generate_files phase=2
recv_files phase=2
recv_files finished
generate_files phase=3
deleting in home
delete_in_dir(home)
[generator] make_file(home/administ,*,2)
Internal error: wrong write used in receiver.
_exit_cleanup(code=2, file
