summaryrefslogtreecommitdiffstats
path: root/SUPPORT
diff options
context:
space:
mode:
authorSubhendu Ghosh <sghosh@users.sourceforge.net>2003-02-09 12:17:48 (GMT)
committerSubhendu Ghosh <sghosh@users.sourceforge.net>2003-02-09 12:17:48 (GMT)
commitf1f19a39a66708d503f3f51e145d275105d960e2 (patch)
treec84abaacb7363d41df0df96ff617d004e5e5df9e /SUPPORT
parent00f86a8f6bfe204e6aa9eb2290ed9f3a8945cebe (diff)
downloadmonitoring-plugins-f1f19a39a66708d503f3f51e145d275105d960e2.tar.gz
ispell
git-svn-id: https://nagiosplug.svn.sourceforge.net/svnroot/nagiosplug/nagiosplug/trunk@296 f882894a-f735-0410-b71e-b25c423dba1c
Diffstat (limited to 'SUPPORT')
-rw-r--r--SUPPORT18
1 files changed, 9 insertions, 9 deletions
diff --git a/SUPPORT b/SUPPORT
index 292c8cb..9dbfd86 100644
--- a/SUPPORT
+++ b/SUPPORT
@@ -4,20 +4,20 @@ also be commercial support options available to you -- check
4http://www.nagios.org/ to track the current status of commercial 4http://www.nagios.org/ to track the current status of commercial
5support offerings. 5support offerings.
6 6
7There are two mailing lits associated wth Nagios Plugin development: 7There are two mailing lists associated with Nagios Plugin development:
8'help' (mailto:nagiosplug-help@lists.sourceforge.net), and 'devel' 8'help' (mailto:nagiosplug-help@lists.sourceforge.net), and 'devel'
9(mailto:nagiosplug-devel@lists.sourceforge.net). Unless you are fairly 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, 10certain you have found a bug or that you are requesting a new feature,
11please direct support requests to 'help'. 11please direct support requests to 'help'.
12 12
13Becuase these lists are handled entirely by voluteers, and because 13Because these lists are handled entirely by volunteers, and because
14these same volunteers are often plugin developers who can also use 14these same volunteers are often plugin developers who can also use
15their time to fix bug and provide feature requests, it is genrally in 15their time to fix bug and provide feature requests, it is generally in
16you interest to do a modest amount of legwork bfore posting to either 16you interest to do a modest amount of legwork before posting to either
17of these lists. 17of these lists.
18 18
19In brief, always provide the version of the software that you are 19In brief, always provide the version of the software that you are
20using, and when requsting features or reporting bugs, first check to 20using, and when requesting features or reporting bugs, first check to
21see that the issue has not already been addressed in the CVS tree. 21see that the issue has not already been addressed in the CVS tree.
22 22
23GETTING HELP 23GETTING HELP
@@ -28,7 +28,7 @@ subject. A good post would have a subject like:
28 28
29 Can I use SSL with check_imap (nagios-plugins 1.3.0-beta2) 1.12 29 Can I use SSL with check_imap (nagios-plugins 1.3.0-beta2) 1.12
30 30
31If you do not include the verion of the plugin, you risk having your 31If you do not include the version of the plugin, you risk having your
32post silently ignored. 32post silently ignored.
33 33
34Be advised that the core plugins (and in fact many of the contributed 34Be advised that the core plugins (and in fact many of the contributed
@@ -46,7 +46,7 @@ Bug reports, investigations of possible bugs, feature requests, and
46patch submissions should be submitted to the development list at 46patch submissions should be submitted to the development list at
47(mailto:nagiosplug-devel@lists.sourceforge.net). 47(mailto:nagiosplug-devel@lists.sourceforge.net).
48 48
49As with the support list, you should identify the version, prefrably 49As with the support list, you should identify the version, preferably
50in the subject line. However, to best use developer resources, it is 50in the subject line. However, to best use developer resources, it is
51suggested that you reference your report one of the following sources: 51suggested that you reference your report one of the following sources:
52 52
@@ -63,7 +63,7 @@ not. However, if you find a bug, you should determine whether it is
63still present in one of these sources, preferably either (2) or (3) 63still present in one of these sources, preferably either (2) or (3)
64which are most recent>) 64which are most recent>)
65 65
66From experince, I know that most bugs can be fixed with only a few 66From 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 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 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 69that time, you ensure that bugs are fixed more rapidly, and thus you