search for: rerr_vanished

https://bugzilla.samba.org/show_bug.cgi?id=9416 Summary: --files-from : RERR_PARTIAL vs RERR_VANISHED Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: penning at uu.nl QAContact: rsy...

...00000000 +0200 +++ log.c 2004-09-05 16:28:42.000000000 +0200 @@ -61,7 +61,7 @@ { RERR_WAITCHILD , "some error returned by waitpid()" }, { RERR_MALLOC , "error allocating core memory buffers" }, { RERR_PARTIAL , "some files could not be transferred" }, - { RERR_VANISHED , "some files vanished before they could be transfered" }, + { RERR_VANISHED , "some files vanished before they could be transferred" }, { RERR_TIMEOUT , "timeout in data send/receive" }, { RERR_CMD_FAILED , "remote shell failed" }, { RERR_CMD_KI...

...I hope this is helpful: Common subdirectories: rsync-2.6.3/doc and rsync-2.6.3_jdb/doc diff -c rsync-2.6.3/errcode.h rsync-2.6.3_jdb/errcode.h *** rsync-2.6.3/errcode.h Mon Dec 15 08:04:14 2003 --- rsync-2.6.3_jdb/errcode.h Tue Mar 15 19:36:28 2005 *************** *** 42,48 **** #define RERR_VANISHED 24 /* file(s) vanished on sender side */ #define RERR_TIMEOUT 30 /* timeout in data send/receive */ ! /* Although it doesn't seem to be specified anywhere, * ssh and the shell seem to return these values: * --- 42,49 ---- #define RERR_VANISHED 24 /* file(s)...

...from Wayne Davidson and JW Schultz suggesting the solution to this, I've patched the rsync-2.5.6 code to acheive this diferentiation with a new RC. If the only errors that occured during an rsync session are 'file not found' when send_files attempts to send the file, then we get RC 24, RERR_VANISHED, and some text to the same effect. I've changed log.c to start the error messsage with "rsync warning" instead of "rsync error" to make it obvious this is not a failure condition. I made these changes on the rsync-2.5.6 code instead of the HEAD stuff in cvs, so I've inc...

Hi all, While trying to mirror a filesystem from one machine to another (for backup purposes) I get the following error: [root@samantha root]# /usr/bin/rsync -qavxzC --delete chandler:/var/ /bigdisk/backup/chandler/dev-md5-var/ root@chandler's password: rsync error: unexplained error (code 24) at main.c(1045) Does this mean anything to anybody? Regards, Graham --

...* ssh and the shell seem to return these values: * diff -Naur rsync-2.6.8/log.c rsync-2.6.8-new/log.c --- rsync-2.6.8/log.c Sat Apr 8 19:04:34 2006 +++ rsync-2.6.8-new/log.c Wed May 24 16:19:27 2006 @@ -83,6 +83,7 @@ { RERR_PARTIAL , "some files could not be transferred" }, { RERR_VANISHED , "some files vanished before they could be transferred" }, { RERR_TIMEOUT , "timeout in data send/receive" }, + { RERR_CON_TIMEOUT, "timeout in connect()" }, { RERR_CMD_FAILED , "remote shell failed" }, { RERR_CMD_KILLED , "remote shell kille...

...me both with and without the --backup-dir option. - The file-list that is output when at least 4 verbose options are specified reports the uid value on the sender even when rsync is not running as root (since we might be sending to a root receiver). - Fixed a typo in the RERR_VANISHED error message. - We once again allow --include/--exclude options to be specified on the server's command-line, even though rsync doesn't use this combination itself (other software does). The parsing of these options now ensures that a daemon transfer can't be to...

...me both with and without the --backup-dir option. - The file-list that is output when at least 4 verbose options are specified reports the uid value on the sender even when rsync is not running as root (since we might be sending to a root receiver). - Fixed a typo in the RERR_VANISHED error message. - We once again allow --include/--exclude options to be specified on the server's command-line, even though rsync doesn't use this combination itself (other software does). The parsing of these options now ensures that a daemon transfer can't be to...

All, I am using rsync to backup a list of files that are in use by an application. Files can be deleted, created, or modified by the application whilst rsync is running. I am getting the following output line, in amongst lots of succesful transfers, when running rsync, : send_files failed to open //ca/spool/smdiq/005.973416/9734161182.1: No such file or directory This then results in an RC of