adding extra tables to NagMIN

[Skip Montanaro]

I have auxiliary info about our system engineers (home, work, cell phones)
which I want to store in a separate NagMIN table keyed by the .  I figured NagMIN would
just ignore my system_engineers table, but I was mistaken:

    Activate Nagios Configuration

    SQL select * from `system_engineers` order by system_engineers_name
    failed : 

Looking at the source for nagios_write.cgi I saw:

    for ($i=0;$i<@titles;$i++) {
            my $ok=1;
            if ($titles[$i] eq "PortScan") { $ok=0; }
            if ($titles[$i] eq "ServiceGroup") { $ok=0; }
            if ($titles[$i] eq "System") { $ok=0; }
            if ($ok) { push(@nagios_tables,$titles[$i]); }
    }

which seemed backwards to me.  Instead of excluding certain tables I think
it should explicitly mention the tables it's interested in.  I submitted a
patch to the NagMIN project:

    http://sourceforge.net/tracker/index.php?func=detail&aid=820273&group_id=77010&atid=548908

which solves the problem I encountered.  Is anyone aware of other places
where NagMIN excludes tables instead of specifically including the ones it
needs?

Thx,

-- 
Skip Montanaro
Got gigs? http://www.musi-cal.com/
          http://www.mojam.com/
Got spam? http://spambayes.sf.net/


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
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