Passive service checks should sometimes reschedule active checks?

[Christopher Gurnee]

Incidentally, I'm looking at Nagios 2.0, I'm not sure what 1.x is
doing...

When a passive service check comes in which triggers a state type change
(hard->soft or soft->hard), I'd think it would be a good idea to
reschedule any associated active service check according to new check
interval (retry_check_interval or normal_check_interval, respectively).
This way, if the max_check_attempts > 1, and retry_check_interval is
much shorter than normal_check_interval, a critical passive service
check will cause an active service check to be executed earlier,
possibly leading to a new critical *hard* state earlier.

As it is now, it looks like a passive service check never causes an
active check to get rescheduled. Would this change make sense?

Thanks for any input,
Chris


P.S. I've attached the patches I posted earlier here (before they
weren't attachments; not sure why I did it that way). Hopefully they
could make their way into the current CVS someday? Please see for
details: 
 
http://sourceforge.net/mailarchive/forum.php?thread_id=4058102&forum_id=
1872

-------------- next part --------------
A non-text attachment was scrubbed...
Name: nagios-last-hostgroups-incorrect.patch
Type: application/octet-stream
Size: 805 bytes
Desc: not available
URL: <https://www.monitoring-lists.org/archive/developers/attachments/20040322/52fdfddf/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nagios-strip-chars-on-notify.patch
Type: application/octet-stream
Size: 2977 bytes
Desc: not available
URL: <https://www.monitoring-lists.org/archive/developers/attachments/20040322/52fdfddf/attachment-0001.obj>