search for: msg_info

Change code to use list_entry api. And removed comment suggesting that change. Signed-off-by: Abhishek Kane <v-abkane at microsoft.com> Signed-off-by: K.Y. Srinivasan <kys at microsoft.com> Signed-off-by: Hank Janssen <hjanssen at microsoft.com> --- drivers/staging/hv/channel_mgmt.c | 17 +++++++++-------- 1 files changed, 9 insertions(+), 8 deletions(-) diff --git

Change code to use list_entry api. And removed comment suggesting that change. Signed-off-by: Abhishek Kane <v-abkane at microsoft.com> Signed-off-by: K.Y. Srinivasan <kys at microsoft.com> Signed-off-by: Hank Janssen <hjanssen at microsoft.com> --- drivers/staging/hv/channel_mgmt.c | 17 +++++++++-------- 1 files changed, 9 insertions(+), 8 deletions(-) diff --git

Hi all, Well, yeah, that's it, really. :-) Try it. Works consistently, on Doze and Linux here ... # rsync -vvrlHSPtiypogD --stats --numeric-ids --delete-after --force -- partial-dir=.partial /tmp/ /var/tmp/ [...show stats...] unknown message 4:1 [generator] rsync error: error in rsync protocol data stream (code 12) at io.c(307) [generator=2.6.9] rsync: connection unexpectedly closed (26

...wayned at samba.org ReportedBy: chris at onthe.net.au QAContact: rsync-qa at samba.org There are at least 2 recursive calls when running --debug=all9: (gdb) bt #1 0x0000000000434996 in perform_io (needed=60, flags=4) at ../rsync/io.c:608 #2 0x0000000000435b71 in send_msg (code=MSG_INFO, buf=0x7fffa60c7da0 "[receiver] perform_io(60, msgroom) needs to flush 33\n", len=53, convert=0) at ../rsync/io.c:955 #3 0x0000000000429840 in rwrite (code=FINFO, buf=0x7fffa60c7da0 "[receiver] perform_io(60, msgroom) needs to flush 33\n", len=53, is_utf8=0) at ../rsync/log.c:2...

...read_loop(fd, buf, 4); redo_list_add(IVAL(buf,0)); break; + case MSG_SUCCESS: + if (len != 4) { + rprintf(FERROR, "invalid message %d:%d\n", tag, len); + exit_cleanup(RERR_STREAMIO); + } + read_loop(fd, buf, 4); + io_multiplex_write(MSG_SUCCESS, buf, 4); + break; case MSG_INFO: case MSG_ERROR: case MSG_LOG: @@ -637,6 +645,16 @@ static int read_unbuffered(int fd, char } read_loop(fd, buffer, remaining); bufferIdx = 0; + break; + case MSG_SUCCESS: + if (remaining != 4) { + rprintf(FERROR, "invalid multi-message %d:%ld\n", + tag, (long...

...trailing comma after the last enum constant. -- albert chin (china@thewrittenword.com) -- snip snip --- rsync.h.orig 2004-05-01 16:52:14.000000000 -0500 +++ rsync.h 2004-05-01 16:52:18.000000000 -0500 @@ -123,7 +123,7 @@ MSG_DATA=0, /* raw data on the multiplexed stream */ MSG_ERROR=FERROR, MSG_INFO=FINFO, MSG_LOG=FLOG, /* remote logging */ MSG_REDO=4, /* reprocess indicated flist index */ - MSG_DONE=5, /* current phase is done */ + MSG_DONE=5 /* current phase is done */ }; #include "errcode.h"

...f rsync. diff -ur src-2.6.2/rsync.h src-2.6.2-local/rsync.h --- src-2.6.2/rsync.h 2004-04-27 03:36:16.000000000 +0200 +++ src-2.6.2-local/rsync.h 2004-08-18 11:36:18.000000000 +0200 @@ -123,7 +123,7 @@ MSG_DATA=0, /* raw data on the multiplexed stream */ MSG_ERROR=FERROR, MSG_INFO=FINFO, MSG_LOG=FLOG, /* remote logging */ MSG_REDO=4, /* reprocess indicated flist index */ - MSG_DONE=5, /* current phase is done */ + MSG_DONE=5 /* current phase is done */ }; #include "errcode.h"

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

...Component: core AssignedTo: wayned@samba.org ReportedBy: hashproduct+rsync@gmail.com QAContact: rsync-qa@samba.org It would be nice if an rsync daemon returned data that the pre-xfer or post-xfer command writes to stdout or stderr to the rsync client in the form of MSG_INFO and MSG_ERROR messages. This enhancement would be good for two reasons: - Pre-xfer and post-xfer commands could report progress and errors to the user. In particular, a pre-xfer command could provide a meaningful error message to accompany rsync's "pre-xfer exec returned failure"....

Hi: I'm in the middle of recoverying from a tactical error copying around an Mac OS X 10.10.5 Time Machine backup (turns out Apple's instructions aren't great...), and I had rsync running for the past 6 hours repairing permissions/acls on 1.5 TB of data (not copying the data), and then it just died in the middle with: .L....og.... 2015-03-11-094807/platinum-bar2/usr/local/mysql