--qVyHzDF4yf4A8jkR
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, May 16, 2006 at 04:03:10PM +0100, Ton Voon wrote:
> Hi Ethan!
>=20
> We found that Nagios is making a host check for every non-OK passive =20
> result received. We don't think that is necessary because if a =20
> passive result is received, then the host must be okay! Details and =20
That is not necessairily true. In distributed mode, one Nagios
might send a service check result to another Nagios via NSCA
hence passive check result. The host being monitored may be
down but you'll still get passive check results for it and don't
want the host assumed up.
However, if this was implemented as a config file option such
that users could invoke this only if they are not running Nagios
in a distributed manner, it would make sense to include it.
Otherwise it probably breaks distributed Nagios behavior.
-Jason Martin
--=20
Programming is an unnatural act.
This message is PGP/MIME signed.
--qVyHzDF4yf4A8jkR
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: --no-verbose
iD8DBQFEagudeDShAkRw0YoRAsEBAJ0cCKaSBtgRbyxpoW3cihGTyfixvACgiTth
G94jfG8+B72V8gAg5MRnn0Q=
=M8ju
-----END PGP SIGNATURE-----
--qVyHzDF4yf4A8jkR--
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]