--YQEH9CATo+4lan7A
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
I'm looking to set up a machine such that several groups can
each own their own Nagios instance. I'd like to be able to set
up a new environment pretty easily as I expect more groups will
want one as the service grows. I forsee a problem with the CGI's
since the path to their config file must be set at compile time.
Although it is feasible to automate a ./configure [..]; make;
make install, I'd like to have all the instance share one set of
binaries.=20
May I suggest that the CGI's be modified to accept the path to
the cgi.cfg from an environmental variable passed from the
webserver? It could function as an override to the compiled-in
default. That way creating a new environment will just require
creating some config dirs and writing some text to the webserver
config.=20
Thanks,
-Jason Martin
--=20
Useless Invention: Papier mache step ladder.
This message is PGP/MIME signed.
--YQEH9CATo+4lan7A
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: --no-verbose
iD8DBQFB6+gcl2ODWuqVSBMRAsr4AJ9ST4fPVGoWVO88GxaILPMnJkeSgACfSWk2
P3WoB2y3JoFFB/WoJevUeUE=
=BOgX
-----END PGP SIGNATURE-----
--YQEH9CATo+4lan7A--
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]