Default value for use_agressive_host_checking (bug-like propertie s)

[Voon, Ton]

Hi!

Wanted to see what other people thought about this because it looked like a
bug to me until I found the use_agressive_host_checking parameter.

I found a situation where a host uses only NRPE to do its service checks.
NRPE is stopped as part of a reboot, so all services are marked as CRITICAL
and the host is DOWN. When the host boots up, NRPE fails to restart.
However, the host is always considered as DOWN, even though pings do work,
because the host check is not run unless use_agressive_host_checking is set
to 1.

I understand there are performance improvements by settign this to 0, but
Nagios appears to be reporting wrong information and that is bad publicity.
Do people think it is a good idea for the default of
use_agressive_host_checking to be 1?

Ton


This private and confidential e-mail has been sent to you by Egg.
The Egg group of companies includes Egg Banking plc
(registered no. 2999842), Egg Financial Products Ltd (registered
no. 3319027) and Egg Investments Ltd (registered no. 3403963) which
carries out investment business on behalf of Egg and is regulated
by the Financial Services Authority.  
Registered in England and Wales. Registered offices: 1 Waterhouse Square,
138-142 Holborn, London EC1N 2NA.
If you are not the intended recipient of this e-mail and have
received it in error, please notify the sender by replying with
'received in error' as the subject and then delete it from your
mailbox.



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
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