I agree what is needed is something very generic that could monitor the
uptime of pretty much any process. After giving this more thought and
always liking to keep things simple here is the direction I might eventually
head. The logic below would result in a log file that shows all unscheduled
outage periods. You would have to ensure it runs at regular intervals.
(NOT VERY PRETTY, BUT SIMPLE ENOUGH)
Files Required:
* Control file that has crontab like entries which define periods that are
either outages or times when database is expected to be running.
Script Workings:
* Run command/script which returns 0 or 1 (0=thingy not running, 1=thingy
running) use separate command/script to log into database, grep for process
etc...
If (( 0 ))
check control file to see if thingy should be running
if suppose to be running
store time & trigger flag (cat time to flag file)
if not suppose to be running
if flag
unscheduled outage was triggered but has rolled into an scheduled
outage period
log start and end time for outage
reset flag
fi
fi
else
if flag
thingy is back up
log start and end time for outage
reset flag
fi
fi
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Post, Ethan
INET: [EMAIL PROTECTED]
Fat City Network Services -- 858-538-5051 http://www.fatcity.com
San Diego, California -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
