You could try errcode.h:
/* error codes returned by rsync */
#define RERR_SYNTAX 1 /* syntax or usage error */
#define RERR_PROTOCOL 2 /* protocol incompatibility */
#define RERR_FILESELECT 3 /* errors selecting input/output files, dirs
*/
#define RERR_UNSUPPORTED 4
Ken,
have a look at errorcode.h in the distribution source of 2.4.6
20 is commented as status returned when sent SIGUSR1 or SIGINT -- the later
being the most useful clue to your problem (you would probably know if you
sent SIGUSR1 to your running rsync.
Greg
> -Original Message-
> Fro
On Wed, May 30, 2001 at 10:50:37AM +1000, Greg Burley <[EMAIL PROTECTED]> wrote:
| have a look at errorcode.h in the distribution source of 2.4.6
| 20 is commented as status returned when sent SIGUSR1 or SIGINT -- the later
| being the most useful clue to your problem (you would probably know if
> "John" == John L Allen writes:
John> But I do agree it would be nice if the man page documented
John> them.
Or, better still, if rsync itself simply told you what they meant ;-)
--- log.c.orig Sat Jan 29 06:35:03 2000
+++ log.c Wed Oct 18 14:01:26 2000
@@ -25,6 +25,29 @
Nice, thanks. Still awaiting your man page patch :-)
-Original Message-
From: Neil Schellenberger [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 30, 2001 10:30 AM
To: [EMAIL PROTECTED]
Subject: RE: rsync exit codes
>>>>> "John" == John L Allen writes:
On Wed, May 30, 2001 at 10:30:07AM -0400, Neil Schellenberger wrote:
Content-Description: message body text
>
> > "John" == John L Allen writes:
>
> John> But I do agree it would be nice if the man page documented
> John> them.
>
> Or, better still, if rsync itself simply told you
> "Dave" == Dave Dykstra <[EMAIL PROTECTED]> writes:
Dave> The source currently in rsync's CVS already does this.
Dave> Martin put that in.
Appologies for the duplicate submission - I have several "local"
patches that I use, and I don't keep good records on which I've
already submitt
