Gregory Machin wrote:
What I want to do is to write a service monitoring daemon, where the
core or body of the script parses a directory, that contains the
config / perl scripts, and is loaded into the core script, if one of
the scripts has an unrecoverable error, it's dumped, thus preserving
the daemon, but more importantly it allows for more inflexibility, as
each script can be tailored to suite that particular service, without
bloating the core script, obviously keeping all good reusable code in
the core script... The script needs to have as few dependencies as
posible as it's going to be run on a custom os thats very minimal ...
and not only will in need to monitor other daemons but also the status
on network interfaces and there connectivity, monitor daemons log
files can carry out actions based on the content, thus also trying to
do preventative maintenance ..
If you want to run scripts, you should use system(). See `perldoc -f
system`
--
Just my 0.00000002 million dollars worth,
Shawn
"For the things we have to learn before we can do them, we learn by
doing them."
Aristotle
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
http://learn.perl.org/
