<pmon-pid-check.pl> script documentation

1. Introduction:
   The purpose of this script is to ensure that the catnrt process is active on the machines "colossus" (OPS LAN) and "xcanuck" (HEAD LAN). The catnrt process is the script that feeds the real-time data to the PMON script that produces the PMON web page. pmon-pid-check.pl is run via CRON every 5 minutes. At run-time, the script reads a file that contains a list of all catnrt processes (stored at /var/tmp/acisdude-colossus-pmon.pid on colossus or /var/tmp/acisdude-xcanuck-pmon.pid xcanuck) started on colossus/xcanuck and grabs the last entry. It then queries the CPU (via `/usr/bin/ps -f -u acisdude') to isolate all the processes being run by 'acisdude'. From that list, it tries to find the catnrt process given the PID from the list of all catnrt processes. If it cannot find it, an email is spawned to `acisdude' indicating it could not find the catnrt process. At the same time, it launches a new catnrt process and appends the date and PID of the new process to the aforementioned log file (stored at /var/tmp/acisdude-colossus-pmon.pid on colossus and /var/tmp/acisdude-xcanuck-pmon.pid on xcanuck).
2. Execution dependencies:
   Requires the process to be run on the machines `colossus' (OPS LAN) and 'xcanuck' (HEAD LAN) and is run every 5 minutes via the CRON daemon.
3. Script dependencies:
   Requires access to the PMON PID file (/var/tmp/acisdude-colossus-pmon.pid and /var/tmp/acisdude-xcanuck-pmon.pid) and the catnrt executable (/home/acisdude/pmon2/catnrt) on colossus and (/home/acisdude/pmon/catnrt) on xcanuck
   

   Scripts used by pmon-pid-check.pl

   catnrt

   Scripts that depend on the outputs

   none

   File dependencies:
   

   Input files:

   /var/tmp/acisdude-[machine]-pmon.pid

   Output files:

   none

4. Code Location and execution
5. Problems and Issues
6. Notes