New to Nagios - Need help with nagios.cfg

[Allan Clark]

On Thu, Feb 19, 2009 at 13:09, Chris Beattie <cbeattie at geninfo.com> wrote:

> Allan Clark wrote:
>
>> Aren't those two files the first duplicates?
>>
>> Remove all *~ files -- I assume your editor created these.  Try again
>> after:
>>
>
> I use gedit to edit my Nagios configuration files, and it's set to make
> backups whose filenames end with a tilde by default.  Nagios ignores them
> since it's looking only for *.cfg, but they do visually pollute the
> directory listing and I tell rsync to exclude them when I copy the config
> files from dev to production.


Indeed, I see it above in the same file (xdata/xodtemplate.c at 978):

                case S_IFREG:
                        x=strlen(dirfile->d_name);
                        if(x<=4 || strcmp(dirfile->d_name+(x-4),".cfg"))
                                break;

Thanks.

In this case, there was a cfg_file and cfg_dir values causing the same file
to be parsed twice, but O.P. is checking another failure now.

Allan
-- 
allanc at chickenandporn.com  "金鱼" http://linkedin.com/in/goldfish
please, no proprietary attachments (http://tinyurl.com/cbgq)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20090219/6b38769a/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null