summaryrefslogtreecommitdiffstats
path: root/SUPPORT
diff options
context:
space:
mode:
Diffstat (limited to 'SUPPORT')
-rw-r--r--SUPPORT71
1 files changed, 71 insertions, 0 deletions
diff --git a/SUPPORT b/SUPPORT
new file mode 100644
index 0000000..292c8cb
--- /dev/null
+++ b/SUPPORT
@@ -0,0 +1,71 @@
1Using the mailing lists and tracker databases at SourceForge are the
2best ways to obtain direct support for the Nagios Plugins. There may
3also be commercial support options available to you -- check
4http://www.nagios.org/ to track the current status of commercial
5support offerings.
6
7There are two mailing lits associated wth Nagios Plugin development:
8'help' (mailto:nagiosplug-help@lists.sourceforge.net), and 'devel'
9(mailto:nagiosplug-devel@lists.sourceforge.net). Unless you are fairly
10certain you have found a bug or thet you are requesting a new feature,
11please direct support requests to 'help'.
12
13Becuase these lists are handled entirely by voluteers, and because
14these same volunteers are often plugin developers who can also use
15their time to fix bug and provide feature requests, it is genrally in
16you interest to do a modest amount of legwork bfore posting to either
17of these lists.
18
19In brief, always provide the version of the software that you are
20using, and when requsting features or reporting bugs, first check to
21see that the issue has not already been addressed in the CVS tree.
22
23GETTING HELP
24
25Requests to 'help' require posting the version number of the
26plugin. The best place to include the version information is in the
27subject. A good post would have a subject like:
28
29 Can I use SSL with check_imap (nagios-plugins 1.3.0-beta2) 1.12
30
31If you do not include the verion of the plugin, you risk having your
32post silently ignored.
33
34Be advised that the core plugins (and in fact many of the contributed
35plugins) will provide a description of their use when invoked with the
36'--help' option. Please read the help carefully and in it's entirety
37before asking for support.
38
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
44
45Bug reports, investigations of possible bugs, feature requests, and
46patch submissions should be submitted to the development list at
47(mailto:nagiosplug-devel@lists.sourceforge.net).
48
49As with the support list, you should identify the version, prefrably
50in the subject line. However, to best use developer resources, it is
51suggested that you reference your report one of the following sources:
52
53 1) The most recent release, including beta's
54
55 2) The twice-daily snapshots (there's a link provided on
56 http://nagiosplug.sourceforge.net)
57
58 3) The current CVS tree from sourceforge
59
60(This does not mean you should run any of these sources in a
61production environment - the latter two you clearly should
62not. However, if you find a bug, you should determine whether it is
63still present in one of these sources, preferably either (2) or (3)
64which are most recent>)
65
66From experince, 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
68present in the CVS tree. If you can save a developer the expense of
69that time, you ensure that bugs are fixed more rapidly, and thus you
70ensure your problem resolution is reflected in a stable release more
71quickly.