> On 16 Oct 2002 at 10:28, Subhendu Ghosh wrote:
>
> >
> > I was going thru the upcoming features list and had a
> > couple of questions/comments.
>
> I just made a few updated to the page, as it hadn't been changed in a
> long time...
>
> >
> > CGI:
> > Even if the move to Fast CGIs is made, having the CGIs read the object
> > config files directly would still cause the CGIs to be out of sync with
> > the running monitor if the monitor was not restarted.
> >
> > Perhaps a "compiled" config created at the the start by the monitoring
> > daemon would prevent the out of sync issue.
>
> Rather than creating a different format for a compiled config file,
> I'll just have the daemon write a single cache file containing all
> object definitions (in raw template format). The CGIs will then be
> able to read that instead of the normal config files. A compiled
> config file would probably be faster than the template-based ones,
> but using FastCGI should nullify that issue.
cache/compile - I guess we both mean the same thing.
>
> >
> > Adaptive monitoring:
> > Also if adaptive monitoring get used - some way to write out the running
> > config would be useful. Otherwise a restart would loose the any changes
> > made. Of course the argument could be made that one must modify the
> > configs as well.
>
> Yep, the format of the retention file (and status log, for that
> matter) will be updated to contain current and normal settings for
> anything that can be changed on-the-fly.
>
Well if you allow hosts and services to be added on-the-fly then we might
obviate the need for config files for some situations!
but small steps first
--
-sg
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: sghosh@sghosh.org