diff options
author | Ton Voon <tonvoon@users.sourceforge.net> | 2004-11-29 23:46:58 +0000 |
---|---|---|
committer | Ton Voon <tonvoon@users.sourceforge.net> | 2004-11-29 23:46:58 +0000 |
commit | fc9a91c513ed85e2869084a9ff614451d62500f3 (patch) | |
tree | 1fab5b21bdf61ad70d2824c8130f54dff99a9e4c /SUPPORT | |
parent | b00c8a2c9f8ab62abb2ce14ba26853cda3df91eb (diff) | |
download | monitoring-plugins-fc9a91c513ed85e2869084a9ff614451d62500f3.tar.gz |
Cleanup and statement re: contrib plugins
git-svn-id: https://nagiosplug.svn.sourceforge.net/svnroot/nagiosplug/nagiosplug/trunk@951 f882894a-f735-0410-b71e-b25c423dba1c
Diffstat (limited to 'SUPPORT')
-rw-r--r-- | SUPPORT | 22 |
1 files changed, 13 insertions, 9 deletions
@@ -1,3 +1,5 @@ | |||
1 | SUPPORT | ||
2 | |||
1 | Using the mailing lists and tracker databases at SourceForge are the | 3 | Using the mailing lists and tracker databases at SourceForge are the |
2 | best ways to obtain direct support for the Nagios Plugins. There may | 4 | best ways to obtain direct support for the Nagios Plugins. There may |
3 | also be commercial support options available to you -- check | 5 | also 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 | |||
16 | you interest to do a modest amount of legwork before posting to either | 18 | you interest to do a modest amount of legwork before posting to either |
17 | of these lists. | 19 | of these lists. |
18 | 20 | ||
21 | Plugins that are in the contrib directories are provided as-is. We will | ||
22 | try to help, but sometimes the plugins have dependencies that the nagios-plugin | ||
23 | developers do not have access to. You may be able to try the authors | ||
24 | directly. | ||
25 | |||
19 | In brief, always provide the version of the software that you are | 26 | In brief, always provide the version of the software that you are |
20 | using, and when requesting features or reporting bugs, first check to | 27 | using, and when requesting features or reporting bugs, first check to |
21 | see that the issue has not already been addressed in the CVS tree. | 28 | see 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 |
37 | before asking for support. | 44 | before asking for support. |
38 | 45 | ||
39 | There is also a support database on the SourceForge-hosted development | ||
40 | site. Feel free to use either the mailing list or the web interface, | ||
41 | but follow the guideline above for both. | ||
42 | |||
43 | REPORTING BUGS AND SUBMITTING PATCHES | 46 | REPORTING BUGS AND SUBMITTING PATCHES |
44 | 47 | ||
45 | Bug reports, investigations of possible bugs, feature requests, and | 48 | Bug reports, investigations of possible bugs, feature requests, and |
46 | patch submissions should be submitted to the development list at | 49 | patch submissions should be submitted to the development list at |
47 | (mailto:nagiosplug-devel@lists.sourceforge.net). | 50 | mailto:nagiosplug-devel@lists.sourceforge.net. Please raise a tracker first |
51 | in Sourceforge, otherwise your email is likely to be missed over time. | ||
48 | 52 | ||
49 | As with the support list, you should identify the version, preferably | 53 | You should identify the version, preferably in the subject line. |
50 | in the subject line. However, to best use developer resources, it is | 54 | However, to best use developer resources, it is suggested that you |
51 | suggested that you reference your report one of the following sources: | 55 | reference 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: | |||
61 | production environment - the latter two you clearly should | 65 | production environment - the latter two you clearly should |
62 | not. However, if you find a bug, you should determine whether it is | 66 | not. However, if you find a bug, you should determine whether it is |
63 | still present in one of these sources, preferably either (2) or (3) | 67 | still present in one of these sources, preferably either (2) or (3) |
64 | which are most recent>) | 68 | which are most recent.) |
65 | 69 | ||
66 | From experience, I know that most bugs can be fixed with only a few | 70 | From experience, I know that most bugs can be fixed with only a few |
67 | more moments work than it takes to determine if the bug is still | 71 | more moments work than it takes to determine if the bug is still |