--00151758f2b8a2149404ca4457e1
Content-Type: text/plain; charset=ISO-8859-1
Also found when I was debugging that read_main_config_file() has only
limited set of nagios directives that it understands.
However it so happens its perfectly legal to have service and host
directives directly in nagios.cfg instead of being included as part of
another file included in there. Granted this configuration is shall we say
unusual, but its not illegal according to current nagios.
To deal with this I've decided to just comment out reporting of error for
UNKNOWN variable (last else) in that function. xdata will report an error
for config directives not recognized.
On Fri, Sep 21, 2012 at 10:35 PM, William Leibzon wrote:
>
> https://github.com/willixix/nagios/comm ... 7e#L0L3474 was
> the cause of issues I see with latest code, so I'm reverting it in my
> branch. And as far as I can tell opts2str function does not actually add
> new lines, at least not in master branch, and in my opinion it shouldn't to
> keep things consistent with new lines added in fcache_host & fcache_service
> just like on other fprintf lines there
>
> Plus to that it did indeed ignore specified path of objects_cache_file,
> but that one was specific to my branch (as a result of another change made
> that was not in sync with my previous changes)
>
>
> On Thu, Sep 20, 2012 at 10:53 PM, William Leibzon wrote:
>
>> mm. something else is wrong, I see that it did the file before getting to
>> xodtemplate. will debug more
>>
>> On Thu, Sep 20, 2012 at 10:23 PM, William Leibzon wrote:
>>
>>>
>>> This did not fix CGIs, those would bypass trying to read main config
>>> file and try to go directly for default cached objects file. This is
>>> in xodtemplate_read_config_data and in addition to that issue macros are
>>> wrong there with #ifdef NSCORE inside #ifdef NSCORE.
>>>
>>> On Sun, Sep 16, 2012 at 2:32 PM, Andreas Ericsson wrote:
>>>
>>>> On 09/16/2012 05:13 PM, Joerg Linge wrote:
>>>> >
>>>> > Am 16.09.2012 um 16:27 schrieb Andreas Ericsson :
>>>> >>
>>>> >> Well, that's by design. The objects.cache should only be written to
>>>> once.
>>>> >> Or do you mean that it gets created but is empty?
>>>> >
>>>> > Correct.
>>>> > object_cache_file was created using the wrong path
>>>> (/usr/local/nagios/var/objects.cache as defined in includes/locations.h
>>>> instead of /omd/sites/ng4/var/nagios/objects.cache defined in nagios.cfg )
>>>> >
>>>> > But the file contains just the header.
>>>> >
>>>>
>>>> Righto. I figured it out and a fix is pushed to both github and to
>>>> svn. Thanks for helping out.
>>>>
>>>> --
>>>> Andreas Ericsson [email protected]
>>>> OP5 AB www.op5.se
>>>> Tel: +46 8-230225 Fax: +46 8-230231
>>>>
>>>> Considering the successes of the wars on alcohol, poverty, drugs and
>>>> terror, I think we should give some serious thought to declaring war
>>>> on peace.
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Everyone hates slow websites. So do we.
>>>> Make your web apps faster with AppDynamics
>>>> Download AppDynamics Lite for free today:
>>>> http://ad.doubleclick.net/clk;258768047;13503038;j?
>>>> http://info.appdynamics.com/FreeJavaPer ... nload.html
>>>> _______________________________________________
>>>> Nagios-devel mailing list
>>>> [email protected]
>>>> https://lists.sourceforge.net/lists/lis ... gios-devel
>>>>
>>>
>>>
>>
>
--00151758f2b8a2149404ca4457e1
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Also found when I was debugging that=A0read_main_config_file() has only lim=
ited set of nagios directives that it understands.Howev=
er it so happens its perfectly legal to have service and host directives di=
rectly in nagios.cfg instead of being included as part of another file incl=
uded in there. Granted this config
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]