samba-bugs@samba.org
2005-Nov-06 19:02 UTC
[Bug 3245] New: error messages not precise enough
https://bugzilla.samba.org/show_bug.cgi?id=3245 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@samba.org ReportedBy: dan1@edenpics.com QAContact: rsync-qa@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 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 -- 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.
Apparently Analagous Threads
- [Bug 3244] New: crash with large directories
- [Bug 3244] crash with large directories
- Sip Phone Won't Login...
- [Bug 3244] exit status with large directories
- DO NOT REPLY [Bug 3935] New: replacing a full directory with symlink with --delete-after produces cryptic message