What about using service templates? That way, the check_period and such are all setup with service template directives, and your service only has to define the command and such.
Thank you, Greg Borbonus *nix System Administrator gregborbo...@gmail.com On 8/10/2010 4:57 AM, mlrtime3 wrote: > I've seen some old threads in the nagios-users group but nothing recent > so I thought I'd bring it up again. > > I have a use case to have a single service defined for 1000's of > different hosts with up to 50-100 different check_period times. > > The only way to do this now is to create a different service with each > check_period. To do this, I would need to create 50-100 different > service definitions for each check_period. > > It makes much more sense for the service to inherit the hosts > check_period value and use this for the service. This allows me to only > define one service. > > Does anyone know of a way to get this to work, or has anyone created a > patch for 3.2.x to do this? > > Thanks, > mlr > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > Nagios-users mailing list > Nagios-users@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 > ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Nagios-users mailing list Nagios-users@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