Bug #11999 perror --ndb option documentation
Submitted: 18 Jul 2005 8:27 Modified: 1 Aug 2005 16:07
Reporter: Hartmut Holzgraefe Email Updates:
Status: Closed Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:4.1, 5.0 OS:Any (*)
Assigned to: Tomas Ulin CPU Architecture:Any

[18 Jul 2005 8:27] Hartmut Holzgraefe
the --ndb option to perror is only documented in the cluster section of the manual,
not in the general section on perror (8.12. perror, Explaining Error Codes)

the option is also not listed in the output of "perror --help"

How to repeat:

  perror --help

or see

[19 Jul 2005 9:00] Hartmut Holzgraefe
The problem with perror --help output is actually that the --ndb option is given
0 as its id as it has no short option character assigned, but it should get an id
>256 in that case as an id of zero is the end marker for my_print_help()

===== perror.c 1.37 vs edited =====
<   {"ndb", 0, "Ndbcluster storage engine specific error codes.",  (gptr*) &ndb_code,
>   {"ndb", 257, "Ndbcluster storage engine specific error codes.",  (gptr*) &ndb_code,
[19 Jul 2005 9:52] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

[19 Jul 2005 10:38] Tomas Ulin
pushed to 4.1.14 (will be merged into 5.1.10)

Please document the switch as well, it has not been done previously
[1 Aug 2005 16:07] Jon Stephens
Thank you for your bug report. This issue has been addressed in the
documentation. The updated documentation will appear on our website
shortly, and will be included in the next release of the relevant

Additional info:

Documented bugfix for 4.1.14 and 5.1.10; updated perror section of RefMan.