Bugzilla – Bug 1274
man: describe vzctl exit codes
Last modified: 2015-04-01 14:45:33 EDT
vzctl has about 50 different exit codes; those should be described in vzctl(8) man page.
Created attachment 984 [details]
Ruby script to create EXIT STATUS section
I used attached script to create the EXIT STATUS section of the new manpage.
Works well and should be quite robust (I tried not to be stricter on the input format than seemed necessary).
"private area with this id already exists":
I propose swapping "already" and "exists" for what I think is better grammar.
Created attachment 985 [details]
Created attachment 986 [details]
Patch against manpage of 3.0.23
Created attachment 987 [details]
Ruby script to create EXIT STATUS section - fixed
When renaming a variable, one should rename it everywhere...
Created attachment 988 [details]
new manpage - fixed
Created attachment 989 [details]
Patch against manpage of 3.0.23 - fixed
Created attachment 990 [details]
Ruby script to create EXIT STATUS section - v3
Maybe it should be said that the script expects vzerror.h on stdin and dumps the manpage formatted text to stdout.
Created attachment 991 [details]
Ruby script to update EXIT STATUS section - v4
Enhanced the script. It now takes the vzctl.8 manpage as input and updates the EXIT STATUS section using ../include/vzerror.h.
Note that your current manpage has no EXIT STATUS, but a DIAGNOSTICS section. Unix seems to suggest to name it EXIT STATUS, so that is how I renamed it.
I should read my email more often...to do less work...
Sorry I have already digged through and documented it and committed it. Here's the patch:
Feel free to further improve it. Again, sorry that your work is lost...
Maybe you can use the descriptions to increase the information in the header file, and then use the script in case of further updates.
Would mean that at least the work is not lost...
Bug was fixed more than one year ago and there were no complains from reporter after fix. We believe bug fix helped and mark bug as closed.