[Samba] samba-tool error messages: what needs fixing most?
billysbobs at yahoo.com
Wed Aug 24 06:33:27 UTC 2022
> > > Q: But won't this break the Application Search-engine Interface (ASI)?
> How will we be able to find old posts on stac^H^H^H^H
> https://lists.samba.org that quote the old nonsensical message?
> A: Yes. ASI stability is never guaranteed. But you can always get the
> old traceback by appending -d3 to your samba-tool line.
Maybe this is what the answer here already says, but as to the questionposed it seems to me that you don't have to give up one to have the other.
The "new" message could simply and plainly give the direct answer, as
you suggest, and then provide the "old" more technical response followingthe new message. This would also have the benefit of providing the moredetailed low level response in the event that for some unforeseen reasonthe problem was something other than the simple answer.
Still further, and along these lines, it would also seem that your proposalneed not be limited to case where there is only one possible simple problemat the root of the error message. In a case where there are severalpossibilities those could be suggested as just that -- potential issues, andthen also followed by the full existing error text.
Not to complicate the endeavor, but this also could be an opportunity tosimply better communicate the detailed low level message.
All in all however, I think that however you decide to implement yourproposal the end end result will be very much welcomed by theSamba user community. Thank you for taking it on.
More information about the samba