diff options
author | Holger Weiss <holger@zedat.fu-berlin.de> | 2014-01-11 16:38:18 (GMT) |
---|---|---|
committer | Holger Weiss <holger@zedat.fu-berlin.de> | 2014-01-11 16:38:18 (GMT) |
commit | 7b0fa5d642466e7cdd0d326658c3c06c27f8a1ec (patch) | |
tree | 1bd1fe366d4063f29ed6930b0750c6bd7a72b7e9 /web/input/doc/faq/reuse.md | |
parent | 16bf58546355690e0d9cf4e7d181255aac73b5c6 (diff) | |
download | site-7b0fa5d642466e7cdd0d326658c3c06c27f8a1ec.tar.gz |
Import most FAQ items from old web site
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
Diffstat (limited to 'web/input/doc/faq/reuse.md')
-rw-r--r-- | web/input/doc/faq/reuse.md | 44 |
1 files changed, 44 insertions, 0 deletions
diff --git a/web/input/doc/faq/reuse.md b/web/input/doc/faq/reuse.md new file mode 100644 index 0000000..6c8e7b0 --- /dev/null +++ b/web/input/doc/faq/reuse.md | |||
@@ -0,0 +1,44 @@ | |||
1 | title: Code reuse | ||
2 | parent: FAQ | ||
3 | --- | ||
4 | |||
5 | # Can I use Nagios Plugins in my project? | ||
6 | |||
7 | Firstly, there is a distinction between a Nagios plugin and plugins from the | ||
8 | Nagios Plugins project. | ||
9 | |||
10 | Although Nagios (the system) is licensed under the GPL, plugins are executed | ||
11 | in their own environment, so they [do not fall][aggregation] under the "viral" | ||
12 | aspect of the GPL. Therefore, any plugin written for use by Nagios can be | ||
13 | under any license the copyright holder selects. | ||
14 | |||
15 | However, the plugins contained within the Nagios Plugins project are | ||
16 | distributed under the [GPL][gpl]. If you distribute an application that | ||
17 | includes the Nagios Plugins (modified or not), you are required to distribute | ||
18 | a copy of the source code for the plugins under the terms of the GPL, | ||
19 | regardless of the licensing for the rest of the application. | ||
20 | |||
21 | If you write a plugin which is a derivative work from code of the Nagios | ||
22 | Plugins project, then your plugin must also be licensed under the GPL, | ||
23 | although you own the copyright for your modified portions. | ||
24 | |||
25 | *Derivative work* usually includes: | ||
26 | |||
27 | * modified versions of the plugins | ||
28 | * other software that contains code (modified or not) copied from the plugins | ||
29 | * other software that `#include`s header files from the plugins | ||
30 | * other software that has linked against library files from the plugins | ||
31 | |||
32 | and does not usually include: | ||
33 | |||
34 | * other software that parses the output of a plugin run from the command line, | ||
35 | exit status, etc. | ||
36 | * software that provides a "wrapper" for command line execution of the plugin | ||
37 | * software that uses status codes and other values which are in the header | ||
38 | files, but also described in the documentation (though not including or | ||
39 | linking to the source) | ||
40 | |||
41 | [aggregation]: http://www.gnu.org/licenses/gpl-faq.html#MereAggregation "GPL FAQ: Mere Aggregation" | ||
42 | [gpl]: http://www.gnu.org/licenses/gpl.html "GPLv3" | ||
43 | |||
44 | <!--% # vim:set filetype=markdown textwidth=78 joinspaces: # %--> | ||