could be used for both the Nagios daemon and the CGI's. It could be
populated by a standalone configuration parser, thereby reducing the
size of the Nagios runtime a little and making uninterrupted
configuration updates possible. BerkeleyDB's atomic transaction support
may be useful for this.
-Al
On Fri, 2003-10-03 at 08:43, Bj=F8rnar Bj=F8rgum Larsen wrote:
> Hello list,
>=20
> 1. There should be a way of letting the nagios process reread its config-=
files without restarting it. Ideally, this would not interrupt ongoing chec=
ks. Any plans to make this happen in 2.0?
>=20
> A couple of ideas on how to make it work, based on how other programs do =
it. From the DNS world:
>=20
> A. The traditional bind / kill -HUP approach. Hmmm. Generally one shouldn=
't have to send signals to a process for it to see that its own configurati=
on has changed. Besides, it can be hard for the process to catch the signal=
in the right way in all possible situations.=20
>=20
> B. The tinydns / make approach. Once you've edited your config files, do =
a "make" (eg. in the etc catalogue). If there's no errors in the config-fil=
es, make will change some other file. For tinydns the config is compiled to=
cdb, not necessarily what we want for Nagios. Anyway, Nagios monitors the =
changes of this file, say every minute, and when it's changed will know it'=
s supposed to reread its configuration. A simplification of this approach w=
ould be to just require users to touch a non-config file in the etc directo=
ry whenever nagios is to reread its config.
>=20
> 2. Other ideas?
>=20
>=20
>
Bj=F8rnar>=20
>=20
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Nagios-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/lis ... gios-devel
** ** ** PRIVILEGED AND CONFIDENTIAL ** ** **
This email transmission contains privileged and confidential information=20
intended only for the use of the individual or entity named above. Any=20
unauthorized review, use, disclosure or distribution is prohibited and=20
may be a violation of law. If you are not the intended recipient or a=20
person responsible for delivering this message to an intended recipient,=20
please delete the email and immediately notify the sender via the email=20
return address or mailto:[email protected]. Thank you.
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]