Why does Socket Timeout immediately send notification?

[timeless]

I have Nagios configured to send notifications after 4 CRITICAL service 
checks. However, if the service check returns "socket timeout," Nagios 
immediately sends the page without doing another 3 checks.

Google searches and searching the documentation/FAQ for "socket timeout" 
only explain what the problem is, not why that sort of failure results 
in an immediate HARD STATE change.

Any clues for me? How can I make it only result in a HARD CRITICAL after 
4 checks, like other CRITICAL events?

-- 
timeless



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
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