NOTES for watchspace.pl <wayne@penguinpowered.org.uk>

UPGRADING?????
--------------
If you're upgrading from an older version, then you need to make a note of all
of your partition and mail settings. These settings are now stored in separate
db files.

SYNOPSIS
--------
This script should be called from cron every 10 or 20 minutes. It checks the
space available on all partitions and warns people if the percentage of used
space on any given partition is too high.

Limits are set by running the accompanying configure.pl script. You can also
use this script to change your settings. At a later date, I will provide a
script that just edits this instead of redoing from scratch.

There is one brane damiged (sic) item about this. It stores the list of failed
partitions in a file on the disk. If the partition that is storing the file is
too full, then the file won't be stored and you will continue to receive
warnings... Or the script may just die and not warn you at all. I'll look at a
better option for this. Any ideas on a fix, please mail
wayne@penguinpowered.org.uk

REQUIREMENTS
------------

This script requires Perl 5 and the following modules :
DB_File
Tie::Hash

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

Check spacewatcher out of cvs or get and untar the tarball
(spacewatcher-1.3.tgz) into the directory above where you want it to run
from.  This will create the directory spacewatcher in your working directory. 

Change the $WORKINGDIR variable at line 88 to point to the real working
directory.

Run the included configure.pl script. This will prompt you for partitions to 
monitor, thresholds to alert at and a To and From e-mail address... Just follow
the script and it should all be ok :-)

Whoever the script is run as will need to be able to write to the working
directory in order to write to the full partitions db. This will automatically
be created on the first run.

Next, add an entry in cron. Example below
0,20,40 * * * * /usr/bin/scripts/watchspace.pl 2>/dev/null
(substitute your working directory for /usr/bin/scripts/)

That's it! You're rolling... Just do a test run of the script to make sure all
paths's etc are healthy.
