Unfortunately, the configuration file is auto-generated from a database; the
object-names used are not under my control.
Names with blanks have been no problem with the old, "default" configuration
system, so I consider this new restriction a bug.
Also, blanks don't show up in the list of restricted characters in
nagios.cfg...
Anyone that can come up with a fix?
Regards,
Florian Kirchmeir
-----Original Message-----
From: Stefano Coletta [mailto:[email protected]]
Sent: Donnerstag, 25. September 2003 17:37
To: [email protected]
Cc: [email protected]
Subject: Re: [Nagios-devel] Nagios-1.1 config file parsing bug
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
>
>
--
Stefano Coletta
http://www.mindcreations.com
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: tefano Coletta [mailto:[email protected]