Config reread issues...

[Christian Hopp]

Moin!

Whenever monit's config changes it reloads it automatically.

-> It should be possible to forbid monit to that automatically, e.g.

        set configreload = [yes|no|manual]

-> If configreload == manual it should be possible to use something
   like "monit reload" to reload the config.


If the new config is buggy and monit is reloading it, monit dies
quite silent (just a syslog entry... no mail!).

-> a) Save the old state before reloading, if it false use the old
      one, if successful the new one.

        How about this... in case of a config change doNOT reload the
        config.  Instead we fork an instance.  This instance loads the
        config.  The original monit "wait"s of the "new" one.
        Depending on the exit value of the child the parsing is
        successful or not.  (Just an idea)

      or

        We have to divide the configuration phase in checking and
        loading.  That means before we load a new config we check if
        it is syntactically correct.

   b) A global email address for monit problems with are not connected
      to any service -> could be default for all services which do not
      state e.g. "alert none".  This global email could be saved and a
      mail could be sent before quiting.


Just some thoughts... which are IMHO very important.  In case the
config might get corrupted by whatever (esp. by the admin) we should
make sure that monit runs on well.


Christian

-- 
Christian Hopp                                email: address@hidden
Institut für Elektrische Informationstechnik             fon: +49-5323-72-2113
TU Clausthal, Leibnizstr. 28, 38678 Clausthal-Zellerf.   fax: +49-5323-72-3197
                             pgpkey: https://www.iei.tu-clausthal.de/pgp-keys/