Escalation notification time shorter than service check time: bug?

[Kelly Jones]

I did this:

define serviceescalation {
 servicegroup_name really-important-services
 first_notification 1
 last_notification 5
 contact_groups level1-oncall
 notification_interval 5
}

define serviceescalation {
 servicegroup_name really-important-services
 first_notification 6
 last_notification 0
 contact_groups level1-oncall,level2-oncall
 notification_interval 5
}

I wanted level1-oncall notified every 5m for 25m when one of
really-important-services went bad, and then level1-oncall and
level2-oncall notified every 5m after 30m.

However, since my service check interval is 20m, level2-oncall didn't
get notified until 6*20m or 120m later.

Nagios didn't warn me about this when I restarted it.

Is this a known bug? Intended behavior? Did I confuse nagios by using
a servicegroup instead of a single service?

-- 
We're just a Bunch Of Regular Guys, a collective group that's trying
to understand and assimilate technology. We feel that resistance to
new ideas and technology is unwise and ultimately futile.

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Register now and save $200. Hurry, offer ends at 11:59 p.m., 
Monday, April 7! Use priority code J8TLD2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
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