4
0

SUPPORT 3.2 KB

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