system should not have whitespaces -- Nagios should follow suit. Maybe a
warning message could be built into the verification stage of Nagios
startup if it sees a whitespace, rather than just ignoring everything
post whitespace?
Jason
Stefano Coletta wrote:
> Do not use spaces for object names and your problem will vanish
>
> [email protected] wrote:
>
>> Hi all!
>>
>> I noticed a problem with the config file parsing code in Nagios 1.1, when
>> using the new (template-based) format:
>> Blanks in various object names (hosts, contact-groups, ...) are not
>> handled
>> correctly when they appear in a list.
>> Example: with a service definition like this:
>>
>> define service{
>> use my_template
>> host_name host a,host b,host c
>> service_description Connectivity Check
>> check_command check_ping
>> }
>>
>> Nagios will complain that host "host" is undefined, instead of looking up
>> "host a".
>>
>> Can anyone please make a patch available? Thanks!
>>
>> Regards,
>> Florian Kirchmeir
>>
>>
>>
>> -------------------------------------------------------
>> This sf.net email is sponsored by:ThinkGeek
>> Welcome to geek heaven.
>> http://thinkgeek.com/sf
>> _______________________________________________
>> Nagios-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/lis ... gios-devel
>>
>>
>
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]