From ad54725251f8dba95177d5aa481e515dd3c16878 Mon Sep 17 00:00:00 2001
From: Holger Weiss <holger@zedat.fu-berlin.de>
Date: Mon, 14 Jul 2014 22:12:06 +0200
Subject: Add FAQ item for migration to Monitoring Plugins

Document the migration from the Nagios Plugins to the Monitoring
Plugins.

diff --git a/web/input/doc/faq/index.md b/web/input/doc/faq/index.md
index bd60afa..c09206a 100644
--- a/web/input/doc/faq/index.md
+++ b/web/input/doc/faq/index.md
@@ -27,6 +27,7 @@ Plugins.
 ## Installing
 
 * [How do I install the plugins?][installation]
+* [How do I migrate to Monitoring Plugins?][migration]
 * [Why aren't the root plugins installed?][root-plugins]
 * [Which user owns the installed plugins?][ownership]
 * [Shouldn't I use a binary package instead?][packages]
@@ -56,6 +57,7 @@ Plugins.
 [mixing-compilers]: doc/faq/mixing-compilers.html
 [ps-on-solaris]: doc/faq/ps-on-solaris.html
 [installation]: doc/faq/installation.html
+[migration]: doc/faq/migration.html
 [root-plugins]: doc/faq/root-plugins.html
 [ownership]: doc/faq/ownership.html
 [packages]: doc/faq/packages.html
diff --git a/web/input/doc/faq/migration.md b/web/input/doc/faq/migration.md
new file mode 100644
index 0000000..3dfd566
--- /dev/null
+++ b/web/input/doc/faq/migration.md
@@ -0,0 +1,45 @@
+title: Migrating to Monitoring Plugins
+parent: FAQ
+---
+
+# How do I migrate to Monitoring Plugins?
+
+If you installed the [Nagios Plugins][nagios-plugins] package in the past and
+now plan to migrate to the Monitoring Plugins, you should check whether your
+operating system vendor provides an official package.  If no such package
+exists, you might have to [install the Monitoring Plugins from
+source][compiling].
+
+You must then make sure the new plugins are found by your monitoring
+application.  While the Nagios Plugins were usually installed into the
+directory `/usr/local/nagios/libexec` when built from the source tarball, the
+Monitoring Plugins are by default installed to `/usr/local/libexec`.  You can
+change this by specifying the `--prefix` option when calling the `./configure`
+script.  For example, the following commands would install the Monitoring
+Plugins into the old location:
+
+    $ ./configure --prefix=/usr/local/nagios
+    $ make
+    $ su root -c 'make install'
+
+If you prefer the new location (`/usr/local/libexec`), you must adjust your
+monitoring application's configuration instead.  The details obviously depend
+on the software you're using.  In typical [Nagios][nagios], [Naemon][naemon],
+and [Icinga 1][icinga-1] setups, the path to the plugins can be modified by
+adjusting the `$USER1$` macro in the `resource_file` (often named
+`resource.cfg`).  With [Icinga 2][icinga-2], you probably want to set the path
+in in your `constants.conf` file, e.g.:
+
+    const PluginDir = "/usr/local/libexec"
+
+If you run into any trouble, please don't hesitate to [contact us][support]!
+
+[nagios-plugins]: http://www.nagios-plugins.org/ "Nagios Plugins"
+[compiling]: doc/faq/compilation.html "Compiling the Monitoring Plugins"
+[icinga-1]: https://www.icinga.org/icinga-1/ "Icinga 1"
+[icinga-2]: https://www.icinga.org/icinga2/ "Icinga 2"
+[naemon]: http://naemon.github.io/ "Naemon"
+[nagios]: http://www.nagios.org/ "Nagios"
+[support]: support.html "Monitoring Plugins Support"
+
+<!--% # vim:set filetype=markdown textwidth=78 joinspaces expandtab: # %-->
-- 
cgit v0.10-9-g596f