$Id: INSTALL,v 1.3 1998/11/29 20:39:41 trockij Exp $

INSTALLATION
------------

-Read the man page for "mon" and "moncmd" in the doc/ directory.

 cd doc
 nroff -man mon.1 | more

-Read the "READMEs" in the doc/ directory for some useful
 insight on system configuration.

-Be sure you have the required Perl modules, which are listed in the
 main README.

-cd mon.d
 make

 to build the RPC monitor.  Keep in mind that if this may fail for
 some reason (it works under Linux, Solaris, and AIX), it is not required
 for the operation of mon itself.

-Make your own mon.cf file, using the suppled "example.cf" (located
 in the etc/ directory) as a template.

-Edit the "auth.cf" file. This file controls which users can perform
 what command. The default is pretty restrictive (read-only), but that's
 only for safety. Currently, "moncmd" is the only client which
 is able to authenticate itself to the server; "mon.cgi" does not
 do authentication yet, and nor does the 2-way pager interface.
 However, these programs work fine in read-only mode.

-You may want to make a DNS CNAME entry called "monhost" for your
 host that will run "mon". You can then set the environment variable
 MONHOST to be this host. "moncmd" uses this variable.

-The Perl scripts look for perl in /usr/bin. You might want to change
 this. I'd advise keeping a locally-installed copy of Perl if you're
 going to monitor network resources and you expect this stuff to work
 when some component of the network is down.

-Test it by starting "mon" from the distribution directory. Use these
 arguments:

./mon -f -c mon.cf -s mon.d -a alert.d

To get see if it's running on your machine:

./clients/moncmd -d list pids

If you get some output, then things are probably OK.

Mon doesn't really need to be installed in any special location.  Just
keep it on the local disk of the machine which will be running the server.

