[Bug 3245] New: error messages not precise enough

samba-bugs at samba.org samba-bugs at samba.org
Sun Nov 6 18:49:12 GMT 2005


           Summary: error messages not precise enough
           Product: rsync
           Version: 2.6.6
          Platform: x86
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P3
         Component: core
        AssignedTo: wayned at samba.org
        ReportedBy: dan1 at edenpics.com
         QAContact: rsync-qa at samba.org

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.


Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

More information about the rsync mailing list