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

1 files changed, 38 insertions, 0 deletions

diff --git a/web/input/doc/faq/ps-on-solaris.md b/web/input/doc/faq/ps-on-solaris.md
new file mode 100644
index 0000000..801c695
--- /dev/null
+++ b/web/input/doc/faq/ps-on-solaris.md
@@ -0,0 +1,38 @@
+title: Process listings on Solaris
+parent: FAQ
+---
+
+# Why use pst3 for check\_procs on Solaris?
+
+Solaris systems restrict the information that is available when you run `ps`.
+On other Unix systems, running `ps` will list you the entire arguments, but
+Solaris restricts the arguments to the first 64 characters at the kernel.
+
+This is a problem if you need to access the arguments to find out a specific
+process (common for listing Java programs).
+
+`/usr/ucb/ps` does list the full arguments, but only for your own processes.
+If you are root, then running `/usr/ucb/ps` can get the full arguments for all
+processes.  However, the columns for `RSS` and `VSZ` merge together when the
+values are too large and check\_procs cannot pull the value out correctly.
+
+The chosen approach is to create our own `ps`-like command, `pst3`.  This
+outputs the required information in a known format for `check_procs` to parse.
+This is the default if you run `./configure` on a Solaris system.
+
+Because `pst3` needs access to some kernel structures, it needs to be compiled
+in 32 and 64 bit modes.
+
+If you are comfortable with the limitations, it is possible to use a Solaris
+`ps` command by specifying these options to `./configure`:
+
+    --with-ps-command="/usr/bin/ps -eo 's uid pid ppid vsz rss pcpu etime comm args'" \
+    --with-ps-format="%s %d %d %d %d %d %f %s %s %n" \
+    --with-ps-cols=10 \
+    --with-ps-varlist="procstat,&procuid,&procpid,&procppid,\
+    &procvsz,&procrss,&procpcpu,procetime,procprog,&pos"
+
+The `--with-ps-varlist` should be on one line - separated here for
+readability.
+
+<!--% # vim:set filetype=markdown textwidth=78 joinspaces: # %-->