R: timeperiods.cfg
Marco Borsani
m.borsani at it.net
Mon Apr 4 15:07:30 CEST 2005
I have read the docs, but the only examples seen are which ones in the
timeperiods.cfg-sample.
Those examples give right to me.
For example:
# 'workhours' timeperiod definition
define timeperiod{
timeperiod_name workhours
alias "Normal" Working Hours
monday 09:00-17:00
tuesday 09:00-17:00
wednesday 09:00-17:00
thursday 09:00-17:00
friday 09:00-17:00
}
It means that notifications/checks will be done all days between 09:00 and
17:00
It seems that my configuration is right!
I want to receive ntotifications between 00:00 and 04:00, between 07:00 and
14:00, between 16:3- and 24:00.
I just ask because all seems to be correct, but last saturaday night arrives
a notification at 03:12 a.m. Where did I wrong ?
Marco
-}> I would't like to check and receive notifications for a service between
-}> 04:00 and 07:00 in the morning and between 14:00 and 16:30 in the
afternoon.
-}> Is it correct use following timeperiod?
-}>
-}> define timeperiod{
-}> timeperiod_name strano
-}> alias strange time
-}> sunday 00:00-04:00,07:00-14:00,16:30-24:00
-}> monday 00:00-04:00,07:00-14:00,16:30-24:00
-}> tuesday 00:00-04:00,07:00-14:00,16:30-24:00
-}> wednesday 00:00-04:00,07:00-14:00,16:30-24:00
-}> thursday 00:00-04:00,07:00-14:00,16:30-24:00
-}> friday 00:00-04:00,07:00-14:00,16:30-24:00
-}> saturday 00:00-04:00,07:00-14:00,16:30-24:00
-}> }
-}>
-}
-}No. This will do the exact opposite of what you want. You need to
-}re-read the docs.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&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
More information about the Users
mailing list