problem with 2.3.3 config parser

Russ Allbery rra at stanford.edu
Mon Oct 7 18:49:23 UTC 2002


patricks <patricks at support.nl> writes:

> I don't know if this is a known problem.

> When you put an comment in the inn.conf files, like this:

> noreader:               true    # comment example

> then the setting will be discarded. The setting will
> only work if the don't put any comment on the same line.

Right.  The old configuration parser was very bad about syntax checking;
it would just ignore the line under various situations without any error
messages.

> The man pages of inn.conf says:

>  "Blank lines and lines starting with a number sign ("#") are ignored."

> But i think a lot of us are used to put commment on the same line as
> well.

Neither the old nor the new (in CURRENT) configuration parser supports
this, but the new configuration parser will give errors and abort reading
inn.conf so that you'll know right away that something is wrong.

This is a bit harder to fix in the old parser.  I may not bother; INN 2.4
shouldn't be too much longer now.

-- 
Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>

    Please send questions to the list rather than mailing me directly.
     <http://www.eyrie.org/~eagle/faqs/questions.html> explains why.


More information about the inn-workers mailing list