Answered my own question: <br>"you can configure Apache to pass an environment variable named
NAGIOS_CGI_CONFIG (which points to the correct location) to the CGIs."<br><br><div class="gmail_quote">On Fri, Jul 3, 2009 at 8:56 AM, Mark Gius <span dir="ltr"><<a href="mailto:mgius@createspace.com">mgius@createspace.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">
The main nagios configuration file is configurable in the init script.
All other files are read based on the cfg_file and cfg_dir directives
in that main nagios configuration file. So you can either use the
default nagios.cfg, which then points to things in /export/nagios, or
edit the init script to also use a nagios.cfg in /export/nagios<br>
<br>
-Gius<br>
<br>
<a href="mailto:megamic@gmail.com" target="_blank">megamic@gmail.com</a> wrote:
<blockquote type="cite"><div><div></div><div class="h5">Hi<br>
<br>
I want to build and install Nagios under a certain path (eg /opt/local)
but tell it to find it's configuration (nagios.cfg, cgi.cfg) elsewhere
(eg /export/nagios). There is useful configure directive for the
lockfile (--with-lockfile), is there something similar for
configuration path? Ideally I don't want to install anything under
/export/nagios as part of the installation procedure, another process
will deploy the correct configuration there, I just want to set Nagios
to look there when it runs.<br>
<br>
Cheers
</div></div><pre><hr size="4" width="90%">
------------------------------------------------------------------------------
</pre>
<pre><hr size="4" width="90%">
_______________________________________________
Nagios-users mailing list
<a href="mailto:Nagios-users@lists.sourceforge.net" target="_blank">Nagios-users@lists.sourceforge.net</a>
<a href="https://lists.sourceforge.net/lists/listinfo/nagios-users" target="_blank">https://lists.sourceforge.net/lists/listinfo/nagios-users</a>
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.
::: Messages without supporting info will risk being sent to /dev/null</pre>
</blockquote>
<br>
</div>
</blockquote></div><br>