Re: Internal error: wrong write used in receiver.
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 rsync-acl-patch, following the second closing brace. Add it and the warning should go away. Matt -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Internal error: wrong write used in receiver.
##
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.
##
--
_
Basem Elkimry
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Internal error: wrong write used in receiver.
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 -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Internal error: wrong write used in receiver.
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 fine without "--delete --force" I thought just --force is the cause of the error but I guess it is --delete Is there a fix for that? Regards, -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Internal error: wrong write used in receiver.
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 code.
..wayne..
--- old/flist.c
+++ new/flist.c
@@ -998,7 +998,7 @@
file->mode = tweak_mode(file->mode, chmod_modes);
#ifdef SUPPORT_ACLS
- if (preserve_acls) {
+ if (preserve_acls && f >= 0) {
sx.st.st_mode = file->mode;
sx.acc_acl = sx.def_acl = NULL;
if (get_acl(fname, &sx) < 0)
@@ -1006,7 +1006,7 @@
}
#endif
#ifdef SUPPORT_XATTRS
- if (preserve_xattrs) {
+ if (preserve_xattrs && f >= 0) {
sx.xattr = NULL;
if (get_xattr(fname, &sx) < 0)
return NULL;
@@ -1021,20 +1021,20 @@
flist->files[flist->count++] = file;
send_file_entry(file, f);
#ifdef SUPPORT_ACLS
- if (preserve_acls)
+ if (preserve_acls && f >= 0)
send_acl(&sx, f);
#endif
#ifdef SUPPORT_XATTRS
- if (preserve_xattrs)
+ if (preserve_xattrs && f >= 0)
send_xattr(&sx, f);
#endif
} else {
#ifdef SUPPORT_ACLS
- if (preserve_acls)
+ if (preserve_acls && f >= 0)
free_acl(&sx);
#endif
#ifdef SUPPORT_XATTRS
- if (preserve_xattrs)
+ if (preserve_xattrs && f >= 0)
free_xattr(&sx);
#endif
}
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Internal error: wrong write used in receiver.
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..
--- old/flist.c
+++ new/flist.c
@@ -987,7 +987,7 @@
file->mode = tweak_mode(file->mode, chmod_modes);
#ifdef SUPPORT_ACLS
- if (preserve_acls) {
+ if (preserve_acls && f >= 0) {
sx.st.st_mode = file->mode;
sx.acc_acl = sx.def_acl = NULL;
if (get_acl(fname, &sx) < 0)
@@ -1003,12 +1003,12 @@
flist->files[flist->count++] = file;
send_file_entry(file, f);
#ifdef SUPPORT_ACLS
- if (preserve_acls)
+ if (preserve_acls && f >= 0)
send_acl(&sx, f);
#endif
} else {
#ifdef SUPPORT_ACLS
- if (preserve_acls)
+ if (preserve_acls && f >= 0)
free_acl(&sx);
#endif
}
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Internal error: wrong write used in receiver.
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=io.c, line=1204): entered _exit_cleanup(code=19, file=main.c, line=1182): entered rsync error: received SIGUSR1 (code 19) at main.c(1182) [receiver=2.6.9] _exit_cleanup(code=19, file=main.c, line=1182): about to call exit(19) rsync error: protocol incompatibility (code 2) at io.c(1204) [generator=2.6.9] _exit_cleanup(code=2, file=io.c, line=1204): about to call exit(2) Used params: -avzR --acls --delete-after --rsh="ssh -l backup" [EMAIL PROTECTED]::home /backup/ Best regards, Sven -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
