New Duplicate definition warnings in 2.0b6

[Fred]

As of 2.0b6 I started seeing lots of duplicate definition warnings such as:

 Warning: Duplicate definition found for service 'loadave' (config file '/opt/hptc/nagios/etc/nj12n16.cfg', starting on line 632)
Warning: Duplicate definition found for service 'loadave' (config file '/opt/hptc/nagios/etc/nj12n16.cfg', starting on line 1031)
Warning: Duplicate definition found for service 'loadave' (config file '/opt/hptc/nagios/etc/nj12n16.cfg', starting on line 1430)
Warning: Duplicate definition found for service 'loadave' (config file '/opt/hptc/nagios/etc/nj12n16.cfg', starting on line 1829)
Warning: Duplicate definition found for service 'loadave' (config file '/opt/hptc/nagios/etc/nj12n16.cfg', starting on line 2574)

These files are autogenerated by a script.  There are indeed service definitions
at these locations that are nearly identical except for the node name.  
(I know I should use hostgroups but I haven't gotten there yet).  

# Service definition
define service{
        use                             nrpe            ; Name of service template to use
                                                                                                                     
        host_name                       nj12n11
        name                            loadave
        service_description             Load Average
        is_volatile                     0
        check_period                    24x7
        max_check_attempts              3
        normal_check_interval           60
        contact_groups                  admins
        active_checks_enabled           0
        passive_checks_enabled          1
# check_load_average is not called here since we are passive
#  Called from check_metrics
        check_command                   check_dummy!1!"load average data is stale"
        register                        1
        }

# Service definition
define service{
        use                             nrpe            ; Name of service template to use
                                                                                                                     
        host_name                       nj12n12
        name                            loadave
        service_description             Load Average
        is_volatile                     0
        check_period                    24x7
        max_check_attempts              3
        normal_check_interval           60
        contact_groups                  admins
        active_checks_enabled           0
        passive_checks_enabled          1
# check_load_average is not called here since we are passive
#  Called from check_metrics
        check_command                   check_dummy!1!"load average data is stale"
        register                        1
        }


Is this really a problem or is it harmless?  

Thanx
-FredC






-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20051213/4f080065/attachment.html>