Nagios Support Forum

william(at)elan.net elan.net> writes:

>
>
> On Wed, 20 Dec 2006, Nicolas COLIN wrote:
>
> > $ patch -p1 > patching file include/common.h
> > Hunk #1 succeeded at 379 (offset -11 lines).
> > patching file include/objects.h
> > Hunk #2 FAILED at 55.
> > 1 out of 2 hunks FAILED -- saving rejects to file include/objects.h.rej
> > patching file p1.pl
>
> Ignore and compile. The failed hunk was to increase hashtree size for
> when you apply one of my other patches (for hostgroupexinfo objects).
>
> > I also looked at nagios-db but it does not seem to evolve frequently.
> > Any of you has already tried it?
>
> Ethan will answer, but I'm under impression that nagios 3.0 will not
> support databases like nagios 2.0 optionally does.
>

Thanks, but the increased size is not enough.

As I do each time I do not succeed resolving a problem, I circumvent it.
The way I found: sending an IFRAME to the FIFO. For example:

[1167321889] PROCESS_SERVICE_CHECK_RESULT;Cach1001;SSI warning;1;

And I send the datas to the HTML corresponding file. Like this:





quantite-date-heure/users/edi/output2/*.*2




So I have not more concerns about the size

If this could help anyone.

Best wishes.

--
Nicolas COLIN.







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