SUPPORT 3.1 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071
  1. Using the mailing lists and tracker databases at SourceForge are the
  2. best ways to obtain direct support for the Nagios Plugins. There may
  3. also be commercial support options available to you -- check
  4. http://www.nagios.org/ to track the current status of commercial
  5. support offerings.
  6. There are two mailing lists associated with Nagios Plugin development:
  7. 'help' (mailto:nagiosplug-help@lists.sourceforge.net), and 'devel'
  8. (mailto:nagiosplug-devel@lists.sourceforge.net). Unless you are fairly
  9. certain you have found a bug or that you are requesting a new feature,
  10. please direct support requests to 'help'.
  11. Because these lists are handled entirely by volunteers, and because
  12. these same volunteers are often plugin developers who can also use
  13. their time to fix bug and provide feature requests, it is generally in
  14. you interest to do a modest amount of legwork before posting to either
  15. of these lists.
  16. In brief, always provide the version of the software that you are
  17. using, and when requesting features or reporting bugs, first check to
  18. see that the issue has not already been addressed in the CVS tree.
  19. GETTING HELP
  20. Requests to 'help' require posting the version number of the
  21. plugin. The best place to include the version information is in the
  22. subject. A good post would have a subject like:
  23. Can I use SSL with check_imap (nagios-plugins 1.3.0-beta2) 1.12
  24. If you do not include the version of the plugin, you risk having your
  25. post silently ignored.
  26. Be advised that the core plugins (and in fact many of the contributed
  27. plugins) will provide a description of their use when invoked with the
  28. '--help' option. Please read the help carefully and in it's entirety
  29. before asking for support.
  30. There is also a support database on the SourceForge-hosted development
  31. site. Feel free to use either the mailing list or the web interface,
  32. but follow the guideline above for both.
  33. REPORTING BUGS AND SUBMITTING PATCHES
  34. Bug reports, investigations of possible bugs, feature requests, and
  35. patch submissions should be submitted to the development list at
  36. (mailto:nagiosplug-devel@lists.sourceforge.net).
  37. As with the support list, you should identify the version, preferably
  38. in the subject line. However, to best use developer resources, it is
  39. suggested that you reference your report one of the following sources:
  40. 1) The most recent release, including beta's
  41. 2) The twice-daily snapshots (there's a link provided on
  42. http://nagiosplug.sourceforge.net)
  43. 3) The current CVS tree from sourceforge
  44. (This does not mean you should run any of these sources in a
  45. production environment - the latter two you clearly should
  46. not. However, if you find a bug, you should determine whether it is
  47. still present in one of these sources, preferably either (2) or (3)
  48. which are most recent>)
  49. From experience, I know that most bugs can be fixed with only a few
  50. more moments work than it takes to determine if the bug is still
  51. present in the CVS tree. If you can save a developer the expense of
  52. that time, you ensure that bugs are fixed more rapidly, and thus you
  53. ensure your problem resolution is reflected in a stable release more
  54. quickly.