1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
|
$Id: INSTALL,v 1.2 1998/07/13 11:52:50 trockij Exp $
INSTALLATION
------------
-Read the man page for "mon" and "moncmd" in the doc/ directory.
-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.
-Make your own mon.cf file, using the suppled "example.cf" (located
in the etc/ directory) as a template. If you've used Big Brother
in the past, you may want to convert your bb-hosts file using
"convert-bb-hosts", and re-write a better config at your leisure.
-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 probably 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:
./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.
|
