f8db90c206
previously, the fragment was sent in the request from client, and the server would parse and increment its value. the incremented value would be set in the redirected URI. this does not work as fragments are meaningless to servers and clients like check_curl strip them in their GET request. rewrite the fragment handling . if client sends a URI parameter with 'fragment' as its key, the server will set its value for its redirected URI. it will come up both as a parameter and the fragment at the end. use this new logic to rewrite the fragment redirection test. remove -p $http_port argument on tests for this endpoint, which was making https tests fail. correct the common test count from 75 to 95, as there are 20 total test assertions in the 8 times it uses the new endpoint. remove unused code on that endpoint as well |
||
|---|---|---|
| .github | ||
| build-aux | ||
| config_test | ||
| doc | ||
| gl | ||
| lib | ||
| m4 | ||
| perlmods | ||
| pkg | ||
| plugins | ||
| plugins-root | ||
| plugins-scripts | ||
| tap | ||
| tools | ||
| .clang-format | ||
| .gitignore | ||
| ABOUT-NLS | ||
| acinclude.m4 | ||
| ACKNOWLEDGEMENTS | ||
| AUTHORS | ||
| autogen.sh | ||
| CODING | ||
| config.rpath | ||
| configure.ac | ||
| COPYING | ||
| FAQ | ||
| Makefile.am | ||
| mkinstalldirs | ||
| NEWS | ||
| NP-VERSION-GEN | ||
| NPTest.pm | ||
| README | ||
| README.md | ||
| REQUIREMENTS | ||
| SUPPORT | ||
| test.pl.in | ||
| THANKS.in | ||
Monitoring Plugins
-
For instructions on installing these plugins for use with your monitoring system, see below. In addition, generic instructions for the GNU toolchain can be found in the
INSTALLfile. -
For major changes between releases, read the
NEWSfile. -
For information on detailed changes that have been made or plugins that have been added, read the
ChangeLogfile. -
Some plugins require that you have additional programs or libraries installed on your system before they can be used. Plugins that are dependent on other programs/libraries that are missing are usually not compiled. Read the
REQUIREMENTSfile for more information. -
Individual plugins are self-documenting. All plugins that comply with the basic guidelines for development will provide detailed help when invoked with the
-hor--helpoptions.
You can check the latest plugins at:
Send an email to help@monitoring-plugins.org for assistance. Please
include the OS type and version that you are using. Also, run the plugin
with the -vvv option and provide the resulting version information. Of
course, there may be additional diagnostic information required as well.
Use good judgment.
Send an email to devel@monitoring-plugins.org for developer discussions.
For patch submissions and bug reports, please use the appropriate resources at:
Installation Instructions
-
If you are using the Git tree, you will need m4, gettext, automake, and autoconf. To start out, run:
./tools/setupFor more detail, see the developer guidelines at https://www.monitoring-plugins.org/doc/guidelines.html.
-
Run the configure script to initialize variables and create a Makefile, etc.
./configure --prefix=BASEDIRECTORY --with-cgiurl=SOMEURLReplace
BASEDIRECTORYwith the path of the directory under which your monitoring system is installed (default is/usr/local), and replaceSOMEURLwith the path used to access the monitoring system CGIs with a web browser (default is/nagios/cgi-bin). -
Compile the plugins with the following command:
make -
Install the compiled plugins and plugin scripts with the following command:
make installThe installation procedure will attempt to place the plugins in a
libexec/subdirectory in the base directory you specified with the--prefixargument to the configure script. -
There are some plugins that require setuid. If you run make install as a non-root user, they will not be installed. To install, switch to root and run:
make install-root
That's it! If you have any problems or questions, feel free to send an email to help@monitoring-plugins.org.
License Notice
You can redistribute and/or modify this software under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version; with the additional exemption that compiling, linking, and/or using OpenSSL is allowed.
This software is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
See the COPYING file for the complete text of the GNU General Public
License, version 3.