Bug 3245 - improve rsync's error messages to make them clearer
improve rsync's error messages to make them clearer
Status: ASSIGNED
Product: rsync
Classification: Unclassified
Component: core
2.6.9
x86 Linux
: P4 enhancement
: ---
Assigned To: Wayne Davison
Rsync QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-11-06 11:49 UTC by Daniel
Modified: 2008-10-02 21:09 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel 2005-11-06 11:49:11 UTC
Generally speaking, it seems that the structure to report an error is badly 
implemented, and makes the error messages not clear enough.
For example, we might get a Code 23 error, but don't know anything about it. 
This makes misconfigurations difficult to find out and makes the mailing list 
far too buzy providing support to all users who don't know about that or this 
problem.

I think that the code should be a bit rewritten as for the output of the 
messages. Normally we can know if there was a memory problem, a disk problem, 
a file that was missing when doing the copy (and which one) or anything else 
and it would be very helpful to print that out to the user. Also, one 
interesting thing would be to assert errors in the code itself so that we 
could know exactly where in the code the problem happened. The current code 
line report normally just specifies the end of a main procedure merely that 
the exact place of the error.

Regards,
Daniel
Comment 1 Matt McCutchen 2008-10-02 21:09:11 UTC
Yes, the code 23 message was bad.  It has been improved:

rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1040) [sender=3.0.4]

Daniel, if you have other specific suggestions, please state them or attach a patch.