Hello,
1) If you are monitoring the checksum of a file, it's, IMHO, for monitoring if someone makes changes on this file, isn'it ? (Personnally, I don't monitor a checksum on a file subject to changes, so Monit do what I expect of it by default). Then, if you change something, monit will trigger an alert. But, if you want, I think you can use exec in order to stop/start this service with a script.
In this case, your checksum will be regenerate (I don't have access to a sandbox for tests with monit, so please check it)
2) Create a script for initialisation. Something like :
monit -g <group name> monitor all
You can unmonitor with : monit -g <group name> unmonitor all.
If you run a script, which do :
/etc/init.d/monit start
monit -g <group name> monitor all
Then, you can run all your service at startup.
Regards,
On Thu, Aug 28, 2008 at 4:43 AM, Art Age Software
<address@hidden> wrote:
Hi,
A couple monit questions:
1. Let's say I have monit monitoring the checksum of a file. I then
make a change to the file which invalidates the checksum. What is the
recommended way to tell monit to regenerate the checksum so that it
does not alert and unmonitor the file, but causing the least impact.
So far, the only thing that has worked for me has been to kill and
restart monit itself.
2. When I restart monit, any "mode manual" services that were
monitored become unmonitored after restart. Is there any way to
restart monit and have it resume monitoring all the services it had
been monitoring prior to restarting, including "mode manual" services?
Thanks for any ideas.
--
To unsubscribe:
http://lists.nongnu.org/mailman/listinfo/monit-general
--
Pierrick Grasland