Re: [Nagios-devel] NDO utils bug/explanation

Guest · Post by **Guest** » Sat Sep 19, 2009 11:42 pm

Hi,

Frassinelli, Marco wrote:

Hello
The process of starting ndo2db
and then Nagios makes
sure that there is actual data within the DB. If there is an outdated data within the DB it
needs to
be removed before Nagios even sends new data. So the process of
trimming those
table entries is truly intentional at the beginning (so-called
pre-launch state
where the if condition matches). If ndo2db fails for some reason, those
data
will remain within the database and then removed during the next start.


Ok, when the parent ndo2db process starts. But not when
the
child starts.

Considering the fact that the process runs daemonized and forks a
child for each ndomod client connection, that is truly wrong. See the
NDOUtils documentation page 8:
http://www.scribd.com/doc/17608352/Nagios-NDOUtils

Going deeper into the code in ndo2db.c:main you will recognize that
after initialization stuff that the standalone daemon condition matches.

        /* standalone daemon... */
        els

...[email truncated]...

This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]