summaryrefslogtreecommitdiffstats
path: root/SUPPORT
diff options
context:
space:
mode:
Diffstat (limited to 'SUPPORT')
-rw-r--r--SUPPORT22
1 files changed, 13 insertions, 9 deletions
diff --git a/SUPPORT b/SUPPORT
index 9dbfd86..5d85207 100644
--- a/SUPPORT
+++ b/SUPPORT
@@ -1,3 +1,5 @@
1SUPPORT
2
1Using the mailing lists and tracker databases at SourceForge are the 3Using the mailing lists and tracker databases at SourceForge are the
2best ways to obtain direct support for the Nagios Plugins. There may 4best ways to obtain direct support for the Nagios Plugins. There may
3also be commercial support options available to you -- check 5also be commercial support options available to you -- check
@@ -16,6 +18,11 @@ their time to fix bug and provide feature requests, it is generally in
16you interest to do a modest amount of legwork before posting to either 18you interest to do a modest amount of legwork before posting to either
17of these lists. 19of these lists.
18 20
21Plugins that are in the contrib directories are provided as-is. We will
22try to help, but sometimes the plugins have dependencies that the nagios-plugin
23developers do not have access to. You may be able to try the authors
24directly.
25
19In brief, always provide the version of the software that you are 26In brief, always provide the version of the software that you are
20using, and when requesting features or reporting bugs, first check to 27using, and when requesting features or reporting bugs, first check to
21see that the issue has not already been addressed in the CVS tree. 28see that the issue has not already been addressed in the CVS tree.
@@ -36,19 +43,16 @@ plugins) will provide a description of their use when invoked with the
36'--help' option. Please read the help carefully and in it's entirety 43'--help' option. Please read the help carefully and in it's entirety
37before asking for support. 44before asking for support.
38 45
39There is also a support database on the SourceForge-hosted development
40site. Feel free to use either the mailing list or the web interface,
41but follow the guideline above for both.
42
43REPORTING BUGS AND SUBMITTING PATCHES 46REPORTING BUGS AND SUBMITTING PATCHES
44 47
45Bug reports, investigations of possible bugs, feature requests, and 48Bug reports, investigations of possible bugs, feature requests, and
46patch submissions should be submitted to the development list at 49patch submissions should be submitted to the development list at
47(mailto:nagiosplug-devel@lists.sourceforge.net). 50mailto:nagiosplug-devel@lists.sourceforge.net. Please raise a tracker first
51in Sourceforge, otherwise your email is likely to be missed over time.
48 52
49As with the support list, you should identify the version, preferably 53You should identify the version, preferably in the subject line.
50in the subject line. However, to best use developer resources, it is 54However, to best use developer resources, it is suggested that you
51suggested that you reference your report one of the following sources: 55reference your report to one of the following sources:
52 56
53 1) The most recent release, including beta's 57 1) The most recent release, including beta's
54 58
@@ -61,7 +65,7 @@ suggested that you reference your report one of the following sources:
61production environment - the latter two you clearly should 65production environment - the latter two you clearly should
62not. However, if you find a bug, you should determine whether it is 66not. However, if you find a bug, you should determine whether it is
63still present in one of these sources, preferably either (2) or (3) 67still present in one of these sources, preferably either (2) or (3)
64which are most recent>) 68which are most recent.)
65 69
66From experience, I know that most bugs can be fixed with only a few 70From experience, I know that most bugs can be fixed with only a few
67more moments work than it takes to determine if the bug is still 71more moments work than it takes to determine if the bug is still