summaryrefslogtreecommitdiffstats
path: root/web/input/doc
diff options
context:
space:
mode:
Diffstat (limited to 'web/input/doc')
-rw-r--r--web/input/doc/faq/compilation.md6
-rw-r--r--web/input/doc/faq/contribute.md2
-rw-r--r--web/input/doc/faq/control.md12
-rw-r--r--web/input/doc/faq/donations.md10
-rw-r--r--web/input/doc/faq/fork.md62
-rw-r--r--web/input/doc/faq/git.md12
-rw-r--r--web/input/doc/faq/gnulib.md4
-rw-r--r--web/input/doc/faq/index.md8
-rw-r--r--web/input/doc/faq/installation.md2
-rw-r--r--web/input/doc/faq/libtap.md7
-rw-r--r--web/input/doc/faq/license.md8
-rw-r--r--web/input/doc/faq/packages.md4
-rw-r--r--web/input/doc/faq/private-c-api.md8
-rw-r--r--web/input/doc/faq/reuse.md12
-rw-r--r--web/input/doc/faq/use-perl-module.md4
-rw-r--r--web/input/doc/index.md6
-rw-r--r--web/input/doc/writing-perl-plugins.md5
17 files changed, 116 insertions, 56 deletions
diff --git a/web/input/doc/faq/compilation.md b/web/input/doc/faq/compilation.md
index ac5fff7..45df8a2 100644
--- a/web/input/doc/faq/compilation.md
+++ b/web/input/doc/faq/compilation.md
@@ -1,4 +1,4 @@
1title: Building Nagios Plugins 1title: Building Monitoring Plugins
2parent: FAQ 2parent: FAQ
3--- 3---
4 4
@@ -6,8 +6,8 @@ parent: FAQ
6 6
7To compile version `1.x` of the plugins, you run: 7To compile version `1.x` of the plugins, you run:
8 8
9 $ gzip -dc nagios-plugins-1.x.tar.gz | tar -xf - 9 $ gzip -dc monitoring-plugins-1.x.tar.gz | tar -xf -
10 $ cd nagios-plugins-1.x 10 $ cd monitoring-plugins-1.x
11 $ ./configure 11 $ ./configure
12 $ make 12 $ make
13 13
diff --git a/web/input/doc/faq/contribute.md b/web/input/doc/faq/contribute.md
index fe97a80..c92594f 100644
--- a/web/input/doc/faq/contribute.md
+++ b/web/input/doc/faq/contribute.md
@@ -16,7 +16,7 @@ you have full rights to it. If your pull request is accepted, we will (of
16course) retain the Git author name and email address, and we'll add your name 16course) retain the Git author name and email address, and we'll add your name
17to the list of contributors in the [THANKS][thanks] file. 17to the list of contributors in the [THANKS][thanks] file.
18 18
19[repo]: https://github.com/nagios-plugins/repositories "Our Repositories" 19[repo]: https://github.com/monitoring-plugins/repositories "Our Repositories"
20[fork]: https://help.github.com/articles/fork-a-repo "Fork Documentation" 20[fork]: https://help.github.com/articles/fork-a-repo "Fork Documentation"
21[pull]: https://help.github.com/articles/using-pull-requests "Pull Request Documentation" 21[pull]: https://help.github.com/articles/using-pull-requests "Pull Request Documentation"
22[github]: https://github.com/ "GitHub" 22[github]: https://github.com/ "GitHub"
diff --git a/web/input/doc/faq/control.md b/web/input/doc/faq/control.md
index 37a811f..59636a0 100644
--- a/web/input/doc/faq/control.md
+++ b/web/input/doc/faq/control.md
@@ -2,15 +2,11 @@ title: Who controls the project?
2parent: FAQ 2parent: FAQ
3--- 3---
4 4
5# Who controls the Nagios Plugins project? 5# Who controls the project?
6 6
7[Nagios Enterprises][enterprises] own the Nagios Plugins project, hence the 7The Monitoring Plugins are maintained by an independent [team][team] of
8domain names of the site belong to Nagios Enterprises. However, the [Nagios 8volunteers.
9Plugins Development Team][team] are responsible for the running of the
10project. This means that decisions about the web site and the development of
11code related to the project are handled independently by the team.
12 9
13[enterprises]: http://www.nagios.com/about/company "Nagios Enterprises" 10[team]: team.html "Monitoring Plugins Development Team"
14[team]: team.html "Nagios Plugins Development Team"
15 11
16<!--% # vim:set filetype=markdown textwidth=78 joinspaces: # %--> 12<!--% # vim:set filetype=markdown textwidth=78 joinspaces: # %-->
diff --git a/web/input/doc/faq/donations.md b/web/input/doc/faq/donations.md
index b7413e9..bc15968 100644
--- a/web/input/doc/faq/donations.md
+++ b/web/input/doc/faq/donations.md
@@ -4,16 +4,16 @@ parent: FAQ
4 4
5# Do you accept donations? 5# Do you accept donations?
6 6
7The [Nagios Plugins Development Team][team] accepts donations for the project. 7The [Monitoring Plugins Development Team][team] accepts donations for the
8We have a separate Paypal account that is used for donations, which is 8project. We have a separate Paypal account that is used for donations, which
9administered by the team leader. 9is administered by the team leader.
10 10
11Donations go towards paying for the small administrative charges we have. We 11Donations go towards paying for the small administrative charges we have. We
12might also use some of the funds for team beer when we meet up in person. 12might also use some of the funds for team beer when we meet up in person.
13 13
14Please contact <donations@nagios-plugins.org> if you're considering a 14Please contact <donations@monitoring-plugins.org> if you're considering a
15donation. 15donation.
16 16
17[team]: team.html "Nagios Plugins Development Team" 17[team]: team.html "Monitoring Plugins Development Team"
18 18
19<!--% # vim:set filetype=markdown textwidth=78 joinspaces: # %--> 19<!--% # vim:set filetype=markdown textwidth=78 joinspaces: # %-->
diff --git a/web/input/doc/faq/fork.md b/web/input/doc/faq/fork.md
new file mode 100644
index 0000000..5057b80
--- /dev/null
+++ b/web/input/doc/faq/fork.md
@@ -0,0 +1,62 @@
1title: Did you fork?
2parent: FAQ
3---
4
5# Did you fork the Nagios Plugins?
6
7TL;DR: No. They forked us.
8
9Long answer:
10
11Initially, there was a Nagios Plugins project. Today, there is both a [Nagios
12Plugins][nagios-plugins] project and a [Monitoring Plugins][monitoring-plugins]
13project. The answer to the question of who forked whom probably isn't
14immediately obvious, especially for those who weren't involved in the mess.
15It'll depend on how exactly you define a "fork", and it may not be all that
16important anyway.
17
18However, because you asked, here's our view on the happenings.
19
20Originally, there was a Nagios Plugins project that was maintained by us;
21i.e., a [team][team] of volunteers not affiliated with [Nagios
22Enterprises][enterprises]. In 2011, we transferred the `nagios-plugins.org`
23domain to Nagios Enterprises on their request. This transfer was coupled with
24an [agreement][agreement] that we would continue to run the project
25independently. Early in 2014, Nagios Enterprises copied most of our web site
26and changed the DNS records to point to their web space instead, which then
27served a slightly modified version of our site including the tarballs we
28created. This was done without prior notice. Presumably, their
29[reasoning][reasoning] for this move was that they weren't happy with us
30[mentioning Icinga and Shinken][mentioning] on our home page.
31
32So, today there are two projects:
33
34One driven by the team that lost its domain, but that did the actual
35maintenance work in the past, and that continues to maintain the same project
36with the same infrastructure (e.g., the GitHub [repositories][repositories]
37and [trackers][trackers], the [mailing lists][support], and the [automated
38test builds][tests]) under the new name.
39
40The other project is driven by the company that controls the domain.
41
42So, if you ask us (as you did by definition when reading this): They clearly
43forked us, not vice versa. We just see two differences to a "typical" fork
44which makes this case less obvious:
45
461. The project that has been forked didn't own its domain name.
472. The project that performed the fork did so without showing any previous
48 development activities.
49
50[nagios-plugins]: http://www.nagios-plugins.org/ "Nagios Plugins"
51[monitoring-plugins]: index.html "Monitoring Plugins"
52[team]: team.html "Monitoring Plugins Development Team"
53[enterprises]: http://www.nagios.com/about/company "Nagios Enterprises"
54[agreement]: news/domain-transfer.html "Domain Transfer Agreement"
55[reasoning]: archive/devel/2014-January/009420.html "Reasoning of Nagios Enterprises"
56[mentioning]: archive/devel/2014-January/009428.html "Response to Nagios Enterprises"
57[repositories]: https://github.com/monitoring-plugins/repositories "GitHub Repositories"
58[trackers]: https://github.com/monitoring-plugins/monitoring-plugins/issues "GitHub Issue Tracker"
59[support]: support.html#mailing-lists "Mailing Lists"
60[tests]: tests.html "Test Results"
61
62<!--% # vim:set filetype=markdown textwidth=78 joinspaces: # %-->
diff --git a/web/input/doc/faq/git.md b/web/input/doc/faq/git.md
index 390b87a..e9bc27d 100644
--- a/web/input/doc/faq/git.md
+++ b/web/input/doc/faq/git.md
@@ -4,9 +4,8 @@ parent: FAQ
4 4
5# How do I use Git? 5# How do I use Git?
6 6
7After the 1.4.13 release, the [Nagios Plugins Development Team][team] moved to 7After the 1.4.13 release, the project moved to [Git][git] for its code
8[Git][git] for its code repositories. This document is a quick introduction 8repositories. This document is a quick introduction to Git.
9to Git.
10 9
11## Basic Concepts 10## Basic Concepts
12 11
@@ -41,14 +40,14 @@ with Git you only have to type a handful of digits to reference one.
41To work on a project you first have to clone it. This creates your own local 40To work on a project you first have to clone it. This creates your own local
42repository, and until you want to distribute your change or merge changes from 41repository, and until you want to distribute your change or merge changes from
43someone else, everything that follows can happen offline. If you have push 42someone else, everything that follows can happen offline. If you have push
44access to the Nagios Plugins repository, run the command: 43access to the Monitoring Plugins repository, run the command:
45 44
46 $ git clone git@github.com:nagios-plugins/nagios-plugins.git 45 $ git clone git@github.com:monitoring-plugins/monitoring-plugins.git
47 46
48If you just want a local copy or wish to clone it to your workstation, you can 47If you just want a local copy or wish to clone it to your workstation, you can
49run this command instead: 48run this command instead:
50 49
51 $ git clone git://github.com/nagios-plugins/nagios-plugins.git 50 $ git clone git://github.com/monitoring-plugins/monitoring-plugins.git
52 51
53This will create a directory called `nagios-plugins` with all the `master` 52This will create a directory called `nagios-plugins` with all the `master`
54code and history (this is roughly equivalent to CVS/SVN `HEAD`). Change 53code and history (this is roughly equivalent to CVS/SVN `HEAD`). Change
@@ -192,7 +191,6 @@ on the [Git web site][git]).
192- Git for Computer Scientists 191- Git for Computer Scientists
193 <http://eagain.net/articles/git-for-computer-scientists/> 192 <http://eagain.net/articles/git-for-computer-scientists/>
194 193
195[team]: team.html "Nagios Plugins Development Team"
196[guidelines]: doc/guidelines.html "Nagios Plugin Development Guidelines" 194[guidelines]: doc/guidelines.html "Nagios Plugin Development Guidelines"
197[git]: http://git-scm.com/ "Git" 195[git]: http://git-scm.com/ "Git"
198[scott]: http://scottchacon.com/ "Scott Chacon" 196[scott]: http://scottchacon.com/ "Scott Chacon"
diff --git a/web/input/doc/faq/gnulib.md b/web/input/doc/faq/gnulib.md
index 5b7299b..964940c 100644
--- a/web/input/doc/faq/gnulib.md
+++ b/web/input/doc/faq/gnulib.md
@@ -12,8 +12,8 @@ latest Gnulib code, do something like:
12 $ cd gnulib 12 $ cd gnulib
13 $ GNULIB_HEAD=$(git rev-parse --short HEAD) 13 $ GNULIB_HEAD=$(git rev-parse --short HEAD)
14 $ cd .. 14 $ cd ..
15 $ git clone git@github.com:nagios-plugins/nagios-plugins.git 15 $ git clone git@github.com:monitoring-plugins/monitoring-plugins.git
16 $ cd nagios-plugins 16 $ cd monitoring-plugins
17 $ ../gnulib/gnulib-tool --update 17 $ ../gnulib/gnulib-tool --update
18 $ find gl -name '*~' -o -name '.gitignore' | xargs rm 18 $ find gl -name '*~' -o -name '.gitignore' | xargs rm
19 $ git status 19 $ git status
diff --git a/web/input/doc/faq/index.md b/web/input/doc/faq/index.md
index 722362c..6b01670 100644
--- a/web/input/doc/faq/index.md
+++ b/web/input/doc/faq/index.md
@@ -4,12 +4,13 @@ parent: Documentation
4 4
5# FAQ 5# FAQ
6 6
7This is a list of Frequently Asked Questions (FAQ) regarding the Nagios 7This is a list of Frequently Asked Questions (FAQ) regarding the Monitoring
8Plugins. 8Plugins.
9 9
10## General 10## General
11 11
12* [Who controls the Nagios Plugins project?][control] 12* [Who controls the project?][control]
13* [Did you fork the Nagios Plugins?][fork]
13* [What license is the code distributed under?][license] 14* [What license is the code distributed under?][license]
14* [Can I submit a patch?][contribute] 15* [Can I submit a patch?][contribute]
15* [Do you accept donations?][donations] 16* [Do you accept donations?][donations]
@@ -41,9 +42,10 @@ Plugins.
41* [How do I use and update Gnulib?][gnulib] 42* [How do I use and update Gnulib?][gnulib]
42* [How do I use the Nagios::Plugin module?][use-perl-module] 43* [How do I use the Nagios::Plugin module?][use-perl-module]
43* [How do I modify NagiosMIB?][nagiosmib] 44* [How do I modify NagiosMIB?][nagiosmib]
44* [Can I use Nagios Plugins in my project?][reuse] 45* [Can I reuse Monitoring Plugins code?][reuse]
45 46
46[control]: doc/faq/control.html 47[control]: doc/faq/control.html
48[fork]: doc/faq/fork.html
47[license]: doc/faq/license.html 49[license]: doc/faq/license.html
48[contribute]: doc/faq/contribute.html 50[contribute]: doc/faq/contribute.html
49[donations]: doc/faq/donations.html 51[donations]: doc/faq/donations.html
diff --git a/web/input/doc/faq/installation.md b/web/input/doc/faq/installation.md
index 6f3694a..f13a9f9 100644
--- a/web/input/doc/faq/installation.md
+++ b/web/input/doc/faq/installation.md
@@ -1,4 +1,4 @@
1title: Installing Nagios Plugins 1title: Installing Monitoring Plugins
2parent: FAQ 2parent: FAQ
3--- 3---
4 4
diff --git a/web/input/doc/faq/libtap.md b/web/input/doc/faq/libtap.md
index c592030..4bd115f 100644
--- a/web/input/doc/faq/libtap.md
+++ b/web/input/doc/faq/libtap.md
@@ -15,10 +15,11 @@ thread implementation. To workaround, run:
15 $ make check 15 $ make check
16 $ make install 16 $ make install
17 17
18Now when you run the Nagios Plugins `./configure` script, it should find the 18Now when you run the Monitoring Plugins `./configure` script, it should find
19libtap library and compile the tests and run them when you run `make` `test`. 19the libtap library and compile the tests and run them when you run `make`
20`test`.
20 21
21*Update:* These days, the Nagios Plugins tarball includes a copy of libtap 22*Update:* These days, the Monitoring Plugins tarball includes a copy of libtap
22which is used if you run `./configure` `--enable-libtap`. 23which is used if you run `./configure` `--enable-libtap`.
23 24
24[libtap]: http://jc.ngo.org.uk/trac-bin/trac.cgi/wiki/LibTap "libtap" 25[libtap]: http://jc.ngo.org.uk/trac-bin/trac.cgi/wiki/LibTap "libtap"
diff --git a/web/input/doc/faq/license.md b/web/input/doc/faq/license.md
index d4a369c..0818b3e 100644
--- a/web/input/doc/faq/license.md
+++ b/web/input/doc/faq/license.md
@@ -4,14 +4,14 @@ parent: FAQ
4 4
5# What license is the code distributed under? 5# What license is the code distributed under?
6 6
7The Nagios Plugins code is currently distributed using the [GNU General Public 7The Monitoring Plugins code is currently distributed using the [GNU General
8License, Version 3][gpl] (GPLv3). 8Public License, Version 3][gpl] (GPLv3).
9 9
10This is because some C code that we depend upon, from the [Gnulib][gnulib] 10This is because some C code that we depend upon, from the [Gnulib][gnulib]
11project, is distributed under the GPLv3; and therefore, some of our plugins 11project, is distributed under the GPLv3; and therefore, some of our plugins
12also need to be GPLv3 licensed. The team has decided, rather than having a 12also need to be GPLv3 licensed. The team has decided, rather than having a
13mixed license, we'll distribute all of the core Nagios Plugins code under the 13mixed license, we'll distribute all of the core Monitoring Plugins code under
14GPLv3. 14the GPLv3.
15 15
16[gpl]: http://www.gnu.org/licenses/gpl.html "GPLv3" 16[gpl]: http://www.gnu.org/licenses/gpl.html "GPLv3"
17[gnulib]: http://www.gnu.org/software/gnulib/ "Gnulib" 17[gnulib]: http://www.gnu.org/software/gnulib/ "Gnulib"
diff --git a/web/input/doc/faq/packages.md b/web/input/doc/faq/packages.md
index 2329db9..d3c1643 100644
--- a/web/input/doc/faq/packages.md
+++ b/web/input/doc/faq/packages.md
@@ -9,8 +9,8 @@ Short answer: **Yes**!
9Slightly longer answer: 9Slightly longer answer:
10 10
11Most Linux distributions and BSD projects provide binary packages of the 11Most Linux distributions and BSD projects provide binary packages of the
12Nagios Plugins. These are usually well-integrated and much easier to deploy 12Monitoring Plugins. These are usually well-integrated and much easier to
13and maintain, so we strongly recommend using them whenever possible. 13deploy and maintain, so we strongly recommend using them whenever possible.
14 14
15Our source tarballs and the associated documentation are primarily intended 15Our source tarballs and the associated documentation are primarily intended
16for package maintainers, for those users who'd like to test them, and for the 16for package maintainers, for those users who'd like to test them, and for the
diff --git a/web/input/doc/faq/private-c-api.md b/web/input/doc/faq/private-c-api.md
index c814d8c..700fd20 100644
--- a/web/input/doc/faq/private-c-api.md
+++ b/web/input/doc/faq/private-c-api.md
@@ -4,8 +4,8 @@ parent: FAQ
4 4
5# Private C APIs 5# Private C APIs
6 6
7This page describes the Nagios Plugins routines that can be accessed from the 7This page describes the Monitoring Plugins routines that can be accessed from
8internal library. 8the internal library.
9 9
10This page is in development, so these are not guaranteed to be available. As 10This page is in development, so these are not guaranteed to be available. As
11the API matures and is available in libraries, this information will be 11the API matures and is available in libraries, this information will be
@@ -15,8 +15,8 @@ migrated to the [Development Guidelines][guidelines].
15 15
16### np\_init(char \*plugin\_name, int argc, char \*\*argv) 16### np\_init(char \*plugin\_name, int argc, char \*\*argv)
17 17
18Initialize the Nagios Plugins routines. Pass the plugin name and `argc` and 18Initialize the Monitoring Plugins routines. Pass the plugin name and `argc`
19`argv` from `main()`. 19and `argv` from `main()`.
20 20
21A variable `nagios_plugin` will be created for internal use. 21A variable `nagios_plugin` will be created for internal use.
22 22
diff --git a/web/input/doc/faq/reuse.md b/web/input/doc/faq/reuse.md
index 6c8e7b0..f7fe8a6 100644
--- a/web/input/doc/faq/reuse.md
+++ b/web/input/doc/faq/reuse.md
@@ -2,21 +2,21 @@ title: Code reuse
2parent: FAQ 2parent: FAQ
3--- 3---
4 4
5# Can I use Nagios Plugins in my project? 5# Can I reuse Monitoring Plugins code?
6 6
7Firstly, there is a distinction between a Nagios plugin and plugins from the 7Firstly, there is a distinction between a Nagios plugin and plugins from the
8Nagios Plugins project. 8Monitoring Plugins project.
9 9
10Although Nagios (the system) is licensed under the GPL, plugins are executed 10Although Nagios (the system) is licensed under the GPL, plugins are executed
11in their own environment, so they [do not fall][aggregation] under the "viral" 11in their own environment, so they [do not fall][aggregation] under the "viral"
12aspect of the GPL. Therefore, any plugin written for use by Nagios can be 12aspect of the GPL. Therefore, any plugin written for use by Nagios can be
13under any license the copyright holder selects. 13under any license the copyright holder selects.
14 14
15However, the plugins contained within the Nagios Plugins project are 15However, the plugins contained within the Monitoring Plugins project are
16distributed under the [GPL][gpl]. If you distribute an application that 16distributed under the [GPL][gpl]. If you distribute an application that
17includes the Nagios Plugins (modified or not), you are required to distribute 17includes the Monitoring Plugins (modified or not), you are required to
18a copy of the source code for the plugins under the terms of the GPL, 18distribute a copy of the source code for the plugins under the terms of the
19regardless of the licensing for the rest of the application. 19GPL, regardless of the licensing for the rest of the application.
20 20
21If you write a plugin which is a derivative work from code of the Nagios 21If you write a plugin which is a derivative work from code of the Nagios
22Plugins project, then your plugin must also be licensed under the GPL, 22Plugins project, then your plugin must also be licensed under the GPL,
diff --git a/web/input/doc/faq/use-perl-module.md b/web/input/doc/faq/use-perl-module.md
index 64ba18a..d624e5f 100644
--- a/web/input/doc/faq/use-perl-module.md
+++ b/web/input/doc/faq/use-perl-module.md
@@ -6,11 +6,11 @@ parent: FAQ
6 6
7The Nagios::Plugin Perl module can be obtained from two main locations: 7The Nagios::Plugin Perl module can be obtained from two main locations:
8 8
9* from the Nagios Plugins tarball with an 9* from the Monitoring Plugins tarball with an
10 [extra configure option][configure-module] 10 [extra configure option][configure-module]
11* from [CPAN][cpan-module] 11* from [CPAN][cpan-module]
12 12
13If you install from the Nagios Plugins tarball, the Perl module will be 13If you install from the Monitoring Plugins tarball, the Perl module will be
14installed in `$prefix/perl`. 14installed in `$prefix/perl`.
15 15
16If you install from CPAN, the Perl module will be installed into your Perl's 16If you install from CPAN, the Perl module will be installed into your Perl's
diff --git a/web/input/doc/index.md b/web/input/doc/index.md
index a7a5bb2..907b2f8 100644
--- a/web/input/doc/index.md
+++ b/web/input/doc/index.md
@@ -7,14 +7,14 @@ menu: 4
7 7
8## Basics 8## Basics
9 9
10The main Nagios Plugins documentation is split into two parts: 10The main Monitoring Plugins documentation is split into two parts:
11 11
121. **[Manual Pages][man]** 121. **[Manual Pages][man]**
13 This part provides documentation for each individual plugin. 13 This part provides documentation for each individual plugin.
14 14
152. **[FAQ][faq]** 152. **[FAQ][faq]**
16 The FAQ section offers additional information on the Nagios Plugins 16 The FAQ section offers information on the Monitoring Plugins package as a
17 package as a whole. 17 whole.
18 18
19## Advanced Topics 19## Advanced Topics
20 20
diff --git a/web/input/doc/writing-perl-plugins.md b/web/input/doc/writing-perl-plugins.md
index 1bee67a..e89d973 100644
--- a/web/input/doc/writing-perl-plugins.md
+++ b/web/input/doc/writing-perl-plugins.md
@@ -4,8 +4,8 @@ parent: Documentation
4 4
5# Writing Perl Plugins 5# Writing Perl Plugins
6 6
7Former Nagios Plugins team lead Ton Voon gave a 15-minutes lightning talk 7Former [team][team] lead Ton Voon gave a 15-minutes lightning talk about
8about the Nagios Plugins at [FOSDEM][fosdem]. He made a screencast of [the 8writing plugins in Perl at [FOSDEM][fosdem]. He made a screencast of [the
9presentation][talk] in Quicktime format (35&nbsp;MB): 9presentation][talk] in Quicktime format (35&nbsp;MB):
10 10
11* [fosdem.mov][screencast] 11* [fosdem.mov][screencast]
@@ -18,6 +18,7 @@ for download, with additional comments:
18Both files are also available via FTP mirrors, see our [download 18Both files are also available via FTP mirrors, see our [download
19page][download]. 19page][download].
20 20
21[team]: team.html "Monitoring Plugins Development Team"
21[fosdem]: https://fosdem.org/ "FOSDEM" 22[fosdem]: https://fosdem.org/ "FOSDEM"
22[talk]: https://archive.fosdem.org/2007/schedule/events/lt_nagios_plugins.html "Ton's Talk" 23[talk]: https://archive.fosdem.org/2007/schedule/events/lt_nagios_plugins.html "Ton's Talk"
23[screencast]: https://www.nagios-plugins.org/download/presentation/fosdem.mov "Screencast" 24[screencast]: https://www.nagios-plugins.org/download/presentation/fosdem.mov "Screencast"