Age | Commit message (Collapse) | Author | Files | Lines |
|
We moved to new Gmane groups below "gmane.network.monitoring.plugins".
|
|
Apply a few changes that hopefully improve the "Did you fork the Nagios
Plugins?" FAQ item a bit.
|
|
Add ftp://mirror.is.co.za/mirror/monitoring-plugins.org/ to our list of
mirrors.
|
|
IRC channel names usually aren't capitalized.
|
|
|
|
Aint the plugin interface "straightforward"?
|
|
|
|
All our previous FTP mirrors except for the one from China were updated
to mirror rsync.monitoring-plugins.org.
|
|
Fix a few remaining references to "nagios-plugins".
|
|
|
|
The snapshot tarballs now use the "monitoring-plugins" name.
|
|
We now host the "Monitoring Plugin Development Guidelines".
|
|
Failing a better sort criteria, lets list monitoring tools in
alphabetical order.
|
|
Thanks to Heiko Schlichting for reporting this issue.
|
|
The Nagios::Plugin module has been renamed to Monitoring::Plugin.
|
|
We moved to #Monitoring-Plugins.
|
|
We need to inform the mirror maintainers of the new project name.
|
|
|
|
This is a first step of replacing the name "Nagios Plugins" with
"Monitoring Plugins" where appriopriate. Some news items and FAQ
entries are also created or updated. More to come.
|
|
"_" should be escaped (to make Vim's syntax highlighting happy, at
least).
|
|
The list is long enough already.
|
|
"presentation.html" is a little too generic.
|
|
Add Ton's "State Retention" RFC to the list of "Proposals" (even though
it has been implemented and documented¹ by now).
¹ https://www.nagios-plugins.org/doc/faq/private-c-api.html#state-information
|
|
"Extra-Opts" is a name.
|
|
Add a few link titles.
|
|
Add ftp://mirror.switch.ch/mirror/nagios-plugins/ to our list of
mirrors.
|
|
Import the "check_many" proposal from our old web site, and add a
"Proposals" section to the Documentation page. Also reference the "New
Threshold Syntax" proposal from there (we didn't link to it before).
|
|
Consistently write `check_foo`, not check\_foo.
|
|
Add a prompt sign to all command lines in code blocks.
|
|
|
|
Stating we accept donations without mentioning how to initiate them
doesn't make much sense.
|
|
Apply a few fixes and improvements throughout the text.
|
|
Clarify the purpose of the staging area, and (try to) improve the "Basic
Concepts" section in another few ways.
|
|
This text was written a few years ago, when we switched from SVN to Git.
These days, it makes less sense to assume the reader is accustomed to
SVN but not to Git.
|
|
While we provide and document our source tarball, we should clarify that
we recommend using distribution-provided binary packages whenever
possible.
|
|
The Nagios Plugin Development Guidelines are referenced on the main
Documentation page (and elsewhere), so there's no need to also mention
them on the Development page.
|
|
Import most of the FAQ entries from our old web site. A few outdated
questions have been omitted, many of the imported ones were updated in
one way or another, and the order of the development-related questions
has been changed. Also, the phrasing of some questions has been
modified (just to make the headings shorter).
For the record, this is the original list of questions from the old web
site:
General
-------
* Who controls the Nagios Plugins project?
* What license is Nagios Plugins distributed under?
* Who owns the copyright for the Nagios Plugin code?
* Can I submit a patch to this project?
* Do you accept donations?
Compiling
---------
* ./configure appears to hang
* check_ldap, check_radius or check_pgsql don't compile even though
configure output says the required libraries are present
* How come check_http/check_tcp doesn't work with --ssl?
* How do I compile the Nagios::Plugin perl module?
* I can't compile check_mysql on solaris
* I get '":types" is not exported by the Params::Validate module' when
running tests
* Why does Solaris use pst3 for check_procs?
Installing
----------
* Some of the root plugins (check_dhcp and check_icmp) haven't been
installed. What's happening?
* Why aren't my plugins installed as the nagios user? And what about
root plugins?
Development
-----------
* How do I use Git?
* Can I add extra tests to the C routines?
* Can I use the Nagios Plugins in my own project?
* How can I find out more about writing a plugin?
* How do I make changes on nagiosmib?
* How do I prove the C routines work?
* How do I use and update Gnulib?
* How do I use the Nagios::Plugin perl module?
* How do the test parameters in NPTest.pm work?
* Private C APIs
|
|
Don't start a new paragraph for the list of mirrors.
|
|
Add an FTP server from Portugal and one from the United States to our
list of mirrors.
|
|
Add the FTP mirrors from Argentina, Belgium, Greece, New Zealand, and
Korea.
|
|
Don't repeat "check"/"checking" that often.
|
|
Add ftp://mirror.bytemark.co.uk/nagios-plugins/ to our list of mirrors.
|
|
Add ftp://mirror.mephi.ru/nagios-plugins/ to our list of mirrors.
|
|
Mention the new FTP mirrors on download.md, and reference that from
doc/presentation.md.
|
|
|
|
... to improve readability a little bit.
|
|
|
|
|
|
Add a link to the /download/mib directory.
|
|
Compared to the Plugins tarballs, the NagiosMIB tarballs aren't all that
popular, so let's hide them away in a subdirectory.
|