John == John L Allen 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 @@
On Wed, May 30, 2001 at 10:30:07AM -0400, Neil Schellenberger wrote:
Content-Description: message body text
John == John L Allen 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
Neil Schellenberger [EMAIL PROTECTED] wrote:
...
(e.g. I seem to remember Dave Dykstra mentioning that certain
server errors were not logged to the client for security
reasons - I may have busted that, sorry).
Dave Martin Tridge will need to decide about that patch. I
Hi,
Where can I find an explanation of rsync's exit codes? I've checked the
man pages and the web site but don't see anything. Specifically, I'm
looking for an explanation of exit status 20?
Thanks,
Ken
(pls reply to me directly, I'm not currently subscribe to the mailing
list. Thanks)
30 /* timeout in data send/receive */
But I do agree it would be nice if the man page documented them.
John.
-Original Message-
From: Ken Versteeg [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 29, 2001 02:18 PM
To: [EMAIL PROTECTED]
Subject: rsync exit codes
Hi,
Where can I
: Ken Versteeg [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, 30 May 2001 4:18 AM
To: [EMAIL PROTECTED]
Subject: rsync exit codes
Hi,
Where can I find an explanation of rsync's exit codes? I've
checked the
man pages and the web site but don't see anything. Specifically, I'm
looking
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
