summaryrefslogtreecommitdiffstats
path: root/SUPPORT
diff options
context:
space:
mode:
Diffstat (limited to 'SUPPORT')
-rw-r--r--SUPPORT35
1 files changed, 18 insertions, 17 deletions
diff --git a/SUPPORT b/SUPPORT
index 5d85207..d2a2b7d 100644
--- a/SUPPORT
+++ b/SUPPORT
@@ -1,14 +1,14 @@
1SUPPORT 1SUPPORT
2 2
3Using the mailing lists and tracker databases at SourceForge are the 3Using the mailing lists and issue tracker at GitHub are the
4best ways to obtain direct support for the Nagios Plugins. There may 4best ways to obtain direct support for the Monitoring Plugins. There may
5also be commercial support options available to you -- check 5also be commercial support options available to you -- check
6http://www.nagios.org/ to track the current status of commercial 6http://www.nagios.org/ to track the current status of commercial
7support offerings. 7support offerings.
8 8
9There are two mailing lists associated with Nagios Plugin development: 9There are two mailing lists associated with Monitoring Plugins development:
10'help' (mailto:nagiosplug-help@lists.sourceforge.net), and 'devel' 10'help' (mailto:help@monitoring-plugins.org), and 'devel'
11(mailto:nagiosplug-devel@lists.sourceforge.net). Unless you are fairly 11(mailto:help@monitoring-plugins.org). Unless you are fairly
12certain you have found a bug or that you are requesting a new feature, 12certain you have found a bug or that you are requesting a new feature,
13please direct support requests to 'help'. 13please direct support requests to 'help'.
14 14
@@ -18,14 +18,15 @@ their time to fix bug and provide feature requests, it is generally in
18you 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
19of these lists. 19of these lists.
20 20
21Plugins that are in the contrib directories are provided as-is. We will 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 22try to help, but sometimes the plugins have dependencies that the monitoring-plugin
23developers do not have access to. You may be able to try the authors 23developers do not have access to. You may be able to try the authors
24directly. 24directly.
25 25
26In brief, always provide the version of the software that you are 26In brief, always provide the version of the software that you are
27using, and when requesting features or reporting bugs, first check to 27using, and when requesting features or reporting bugs, first check to
28see that the issue has not already been addressed in the CVS tree. 28see that the issue has not already been addressed in the current Git
29code.
29 30
30GETTING HELP 31GETTING HELP
31 32
@@ -33,7 +34,7 @@ Requests to 'help' require posting the version number of the
33plugin. The best place to include the version information is in the 34plugin. The best place to include the version information is in the
34subject. A good post would have a subject like: 35subject. A good post would have a subject like:
35 36
36 Can I use SSL with check_imap (nagios-plugins 1.3.0-beta2) 1.12 37 Can I use SSL with check_imap (monitoring-plugins 1.3.0-beta2) 1.12
37 38
38If you do not include the version of the plugin, you risk having your 39If you do not include the version of the plugin, you risk having your
39post silently ignored. 40post silently ignored.
@@ -47,19 +48,19 @@ REPORTING BUGS AND SUBMITTING PATCHES
47 48
48Bug reports, investigations of possible bugs, feature requests, and 49Bug reports, investigations of possible bugs, feature requests, and
49patch submissions should be submitted to the development list at 50patch submissions should be submitted to the development list at
50mailto:nagiosplug-devel@lists.sourceforge.net. Please raise a tracker first 51mailto:devel@monitoring-plugins.org. Please raise an issue first
51in Sourceforge, otherwise your email is likely to be missed over time. 52in GitHub, otherwise your email is likely to be missed over time.
52 53
53You should identify the version, preferably in the subject line. 54You should identify the version, preferably in the subject line.
54However, to best use developer resources, it is suggested that you 55However, to best use developer resources, it is suggested that you
55reference your report to one of the following sources: 56reference your report to one of the following sources:
56 57
57 1) The most recent release, including beta's 58 1) The most recent release, including beta's
58 59
59 2) The twice-daily snapshots (there's a link provided on 60 2) The current snapshots (there's a link provided on
60 http://nagiosplug.sourceforge.net) 61 https://www.monitoring-plugins.org/download.html)
61 62
62 3) The current CVS tree from sourceforge 63 3) The current Git code from GitHub
63 64
64(This does not mean you should run any of these sources in a 65(This does not mean you should run any of these sources in a
65production environment - the latter two you clearly should 66production environment - the latter two you clearly should
@@ -69,7 +70,7 @@ which are most recent.)
69 70
70From experience, I know that most bugs can be fixed with only a few 71From experience, I know that most bugs can be fixed with only a few
71more moments work than it takes to determine if the bug is still 72more moments work than it takes to determine if the bug is still
72present in the CVS tree. If you can save a developer the expense of 73present in the Git tree. If you can save a developer the expense of
73that time, you ensure that bugs are fixed more rapidly, and thus you 74that time, you ensure that bugs are fixed more rapidly, and thus you
74ensure your problem resolution is reflected in a stable release more 75ensure your problem resolution is reflected in a stable release more
75quickly. 76quickly.