I got frustrated trying to show someone how to install mon, so I rewrote
chunks of the INSTALL doc to match reality. Apply or ignore as you see fit.
--
Eric Sorenson - Systems / Network Administrator, MIS - Transmeta Corporation
diff -urN mon-1.0.0pre2-orig/INSTALL mon-1.0.0pre2/INSTALL
--- mon-1.0.0pre2-orig/INSTALL 2004-06-18 07:40:10.000000000 -0700
+++ mon-1.0.0pre2/INSTALL 2004-07-07 11:20:48.000000000 -0700
@@ -1,79 +1,105 @@
$Id: INSTALL,v 1.1.1.1.2.2 2004/06/18 14:40:10 trockij Exp $
-INSTALLATION
-------------
+OVERVIEW
+--------
-Several parts:
-
- 1. mon, the server
-
- 2. Mon::Client, the Perl library used by some clients.
+There are several components you'll need to get working to
+have a fully functional mon installation.
+ 1. mon, the server
+ 2. Mon::Client, the Perl library used by some clients
3. C programs in mon.d
+ 4. Optional (but highly useful) monitors
+ 5. A customized mon.cf to make the server do what you want
-REQUIREMENTS
-------------
+1. MON SERVER
+-------------
-The "mon" daemon uses Perl 5.n, where n >= 005_01. Older versions of Perl had
-problems with Sys::Syslog under Linux, and had dated versions of
-Text::ParseWords. Mon also requires that *.ph be created from the system
-header files. If you're using a pre-packaged Perl (such as from RedHat) then
-this has been done for you already. Otherwise, this is done manually during
-Perl installation by these means:
+The "mon" daemon uses Perl 5.n, where n >= 005_01.
+
+Mon requires that *.ph be created from the system header files. If you try to
+run mon and Perl complains with the "did you run h2ph?" message, then chances
+are this step wasn't done, either by your package manager or manually after
+Perl installation. You can fix it by doing the following, as root:
cd /usr/include
- h2ph *.h sys/*.h
+ h2ph -r -l .
-However, if you're running Linux you may need to run
+You'll need the following modules for the server to function, all of
+which are available from your nearest CPAN archive. The listed
+CPAN paths relative to /cpan/modules/by-authors/id/ -- versions of
+modules on CPAN change quickly, so there may be newer versions available,
+but the following are known to work:
- cd /usr/include
- h2ph *.h sys/*.h asm/*.h
+ Time::Period PRYAN/Period-1.20.tar.gz
+ Time::HiRes J/JH/JHI/Time-HiRes-1.59.tar.gz
+ Convert::BER G/GB/GBARR/Convert-BER-1.3101.tar.gz
-If you try to run mon and Perl complains with the "did you run h2ph?"
-message, then chances are this step wasn't done.
-You'll need the following modules for the server to function, all of
-which are available from your nearest CPAN archive, or the place
-where you got mon:
+2. INSTALLING THE PERL CLIENT MODULE
+------------------------------------
+
+The Perl client module is distributed as a separate package. It is named
+"mon-client-*.tar.gz". Refer to that for installation instructions.
+It is available on kernel.org mirrors in the /pub/software/admin/mon directory,
+and in CVS on sourceforge.net. Be sure to match the version of mon-client with
+the version of mon you are using. At this time, branch "mon-1-0-0pre1" of the
+mon CVS module matches the "mon-client-1-0-0pre1" branch of the mon-client CVS
+module. See http://sourceforge.net/projects/mon/ for information on CVS access.
+
+
+3. COMPILING THE C CODE (optional)
+----------------------------------
+
+Some of the monitors included with mon are written in C and need to
+be compiled for your system. If you want to use the RPC monitor or the
+dialin.monitor wrapper,
+
+ cd mon.d
+ (edit Makefile)
+ make
+ make install
+ cd ..
+
+Keep in mind that although this is known to work on Linux, Solaris, and AIX,
+it may not compile on your system. It is not required for the operation of mon
+itself.
- -Time::Period (the one written by Patrick Ryan)
- -Time::HiRes
- -Convert::BER
- -Mon::*
+
+4. MONITORS
+-----------
All of the monitor and alert scripts that are packaged with mon are
actually *optional*. However, this is what you'll need for each special
-monitor:
+monitor, with CPAN paths relative to /cpan/modules/by-author/id/
+
+ freespace.monitor - requires Filesys::Diskspace from CPAN,
+ in FTASSIN/Filesys-DiskSpace-0.05.tar.gz
+
- freespace.monitor
- The disk space monitor requires the "Filesys::DiskSpace" Perl
- module from CPAN.
-
- fping.monitor
- Requires the "fping" code, probably available from the same
- place that you got this package.
-
- telnet.monitor
- This requires the Net::Telnet Perl module, available from
- CPAN.
+ fping.monitor - requires the 'fping' binary, from http://www.fping.com
+ RPM packages available at http://dag.wieers.com/packages/fping/
+
+ telnet.monitor - requires the Net::Telnet from CPAN,
+ in J/JR/JROGERS/Net-Telnet-3.03.tar.gz
reboot.monitor
asyncreboot.monitor
netappfree.monitor
process.monitor
hpnp.monitor
- All use the UCD SNMP 3.6.3, along with G.S. Marzot's
- Perl module.
-
- ldap.monitor
- requires the Net::LDAPapi Perl module, available from CPAN.
+ Use the 'net-snmp' package (formerly UCD SNMP), from
+ http://sourceforge.net/projects/net-snmp
+ with G.S. Marzot's Perl module G/GS/GSM/SNMP-4.2.0.tar.gz
+
+ ldap.monitor - requires Net::LDAPapi from CPAN,
+ CDONLEY/Net-LDAPapi-1.42.tar.gz
+ dialin.monitor - requires the Perl Expect module from CPAN,
+ R/RG/RGIERSIG/Expect-1.15.tar.gz
- dialin.monitor
- requires the Perl Expect module, available from CPAN.
-
- dns.monitor
- requires the Net::DNS Perl module.
+ dns.monitor - requires Net::DNS from CPAN,
+ C/CR/CREIN/Net-DNS-0.47.tar.gz
msql-mysql.monitor
requires the MSQL/MySQL DBD module and DBI front-end.
@@ -82,30 +108,11 @@
above, so please take the time to read doc/README.monitors to get the
details.
-
-1. INSTALLING THE PERL CLIENT MODULE
-------------------------------------
-
-The Perl client module is distributed as a separate package. It is named
-"mon-client-*.tar.gz". Refer to that for installation instructions. This
-module is available in CPAN (http://www.perl.com/CPAN/), on kernel.org mirrors
-in the /pub/software/admin/mon directory, and in CVS on sourceforge.net.
-Be sure to match the version of mon-client with the version of mon you
-are using.
-
-If you are using a CVS release of the mon server, you will want
-to be sure to match it with the corresponding version from the
-"mon-client" module. At this time, branch "mon-1-0-0pre1" of the
-mon CVS module matches the "mon-client-1-0-0pre1" branch of the
-mon-client CVS module. See http://sourceforge.net/projects/mon/ for
-information on CVS access.
-
-
-2. MON SERVER INSTALLATION
---------------------------
+5. MON.CF CUSTOMIZATION AND STARTUP
+-----------------------------------
-Read the man page for "mon" and "moncmd" in the doc/ directory to get
- an overview about the directories involved, i.e. the configuration,
+ an overview of the directories involved, i.e. the configuration,
alert, monitors, state, and run directories.
cd doc
@@ -168,15 +175,3 @@
keep it on the local disk of the machine which will be running the server.
-3. COMPILING THE C CODE (optional)
-----------------------------------
-
--cd mon.d
- (edit Makefile)
- make
- make install
- cd ..
-
- to build the RPC monitor and the dialin.monitor wrapper. 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.
_______________________________________________
mon mailing list
[EMAIL PROTECTED]
http://linux.kernel.org/mailman/listinfo/mon
