Heads up: Comments might bite you; was Re: Possible bug in 3.0rc3

[Tobias Klausmann]

Hi! 

Actually, this was both my and Nagios' fault. You see, faced with
a config block like this:

# foo=bar\
foo=baz

Nagios will see... nothing. The trailing \ in the first line
joins up the second and then both disappear since it's now one
long comment.

Logic-wise I'd say it's 50/50 bug/feature. I personally think
that a # should have precedence over \-at-eol. Usability-wise
it's definitely a bug and I've said as much on -devel.

Still, a nasty trap to fall into. Beware when you next edit your
configs.

Regards,
Tobias

PS: It seems this behaviour was introduced somewhere between b7
and rc3, probably when adding line continuation support.

-- 
"Have you any idea how successful censorship is on TV?
 Don't know the answer?  Hm.  Successful, isn't it?" -Max Headroom

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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