------=_Part_69875_24283883.1221251730168
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Yes,
On Fri, Sep 12, 2008 at 6:13 AM, Hendrik B=8A=E4cker wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> Marcel schrieb:
> > I think i've found a bug.
> >
> > in config.c:
> >
> > At line #1878, temp_service->check_interval is incorrectly assuming
> > interval_lenght=3D60, but if one would use an interval_length directive
> > equals to 1, then the Warnings like: "[1220575781] Warning: Service
> > 'Current Load' on host 'faeroes' has a notification interval less than
> > its check interval! Notifications are only re-sent after checks are
> > made, so the effective notification interval will be that of the check
> > interval." will incorrectly shows up, because the conditional below
> > assumes interval_lenght =3D 60.
> >
> Do have a configuration example to rebuild your mentioned problem?
> I am using interval_length=3D1 and doesn't recognize any of your warning
> messages cause of mismatching check/notification interval.
If you have a service that would be checked every 10 seconds, and
notification interval =3D 60, then you should get the warning message.
And yes, it is against 3.0.3 cvs code.
Cheers
Marcel
------=_Part_69875_24283883.1221251730168
Content-Type: text/html; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Yes,On Fri, Sep 12, 200=
8 at 6:13 AM, Hendrik B=8A=E4cker <[email protected]> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Marcel schrieb:
> I think i've found a bug.
>
> in config.c:
>
> At line #1878, temp_service->check_interval is incorrectly assuming=
> interval_lenght=3D60, but if one would use an interval_length directiv=
e
> equals to 1, then the Warnings like: "[1220575781] Warning: Servi=
ce
> 'Current Load' on host 'faeroes' has a notificat=
ion interval less than
> its check interval! Notifications are only re-sent after checks =
are
> made, so the effective notification interval will be that of the check=
> interval." will incorrectly shows up, because the conditional bel=
ow
> assumes interval_lenght =3D 60.
>
Do have a configuration example to rebuild your mentioned problem?
I am using interval_length=3D1 and doesn't recognize any of your warnin=
g
messages cause of mismatching check/notification interval.If you have a service that would be checked every 10 seconds, and =
notification interval =3D 60, then you should get the warning message.
And yes, it is against 3.0.3 cvs code. CheersMarcel
------=_Part_69875_24283883.1221251730168--
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]