-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Explain return code in man page #28
Comments
Hi Didier, I was surprised to realize the man pages don't document return codes. They absolutely should do this, and I'll fix this in the next release. Until then, here's a quick summary of how things are intended to work:
Right now there might be an exception or two to these rules; I see one spot in core/msystem.cpp that would exit with -1, but it's right below a comment saying "should never happen ...", and I doubt anyone will bump into it in practice. I think I'll change this and any other exceptions I run across at the same time I update the man pages. |
thank you brian. Have you a date for the next release ? |
I don't have an exact date, but it will probably be sometime in December or January. |
I've added Exit Code sections to the man pages on this branch: https://github.com/Tripwire/tripwire-open-source/tree/dev/q1-2018 . I have some other documentation stuff to do there before it becomes a 2.4.3.7 release, but I hope to have that wrapped up in the near future. |
Resolved in 2.4.3.7 |
Closing as resolved. |
Hi there,
I need some information about return code. I try to look into code, but it's very difficult to have a complete list. It will be very nice to add this in man page.
Thank in advance,
Didier.
The text was updated successfully, but these errors were encountered: