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
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.
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.