RE: Feature request for config file checking?

[Jan-Henrik Haukeland]

Actually, this functionality has existed in monit up until the 3.2 release.
We had a discussion on the developer list[1] (starting with this mail:
 http://mail.nongnu.org/archive/html/monit-dev/2003-01/msg00081.html)
and decided to *not* automatically reload the control file in the latest
release.

You can read more about the rationale for this decision in the thread starting
with the mail mentioned in the link above.

Anyway the good news is that monit will reload the monitrc control file upon
receiving the SIGHUP signal (this info should be in the documentation). If it
is
problematic to send a SIGHUP signal to running monit daemons on several
machines
after you have distributed a new monitrc control file we may and should
probably
add this functionality to the web-interface as well so you can call a certain
URL
from a script to update a running monit daemon like with such an URL:
 http//IP-ADDRESS:2812/_reload

What do you think?

Jan-Henrik


[1] We (i.e. the developers in the monit project ) should in the future strive
to bring functionality changes on this level to this mailing list so others may
take part in the discussion or at least get the information without having to
subscribe to the monit developer list.


> -----Original Message-----
> From: address@hidden
> [mailto:address@hidden Behalf
> Of Mark Ferlatte
> Sent: 3. juni 2003 21:00
> To: address@hidden
> Subject: Feature request for config file checking?
>
>
> Hi all,
>
> I've got a large cluster of machines that are all imaged from a
> central server.
> What happens currently is that sometimes a config gets changed on the master
> image, gets pushed out, but the daemons don't get restarted.
>
> So, since I'm already using monit to see if the daemons are actually running,
> it seemed like it would make sense for monit to check to see if the
> config file
> had changed since the daemon had started and take an action...
> something like:
>
> check apache with pidfile /var/run/apache.pid
>   start program = /etc/init.d/apache start
>   stop program = /etc/init.d/apache stop
>   checkconfig /etc/apache/httpd.conf and restart on changed checksum
>
> Is this something that would be interesting?  You can almost do it
> already, but
> you need to embed a checksum into the configfile, which is not what I want: I
> want monit to checksum the file on startup, and then check it
> periodically and
> restart the daemon if that checksum changes.
>
> M
>