-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 06/08/2013 17:17, Marek Vavrusa wrote:
Hi Marek,
I see. It's quite unfortunate that I allowed
unquoted strings in
the configuration, so this complicates the checking for boolean a
bit. I am thinking of disallowing unquoted strings in the next
release, hope there's no big fan of this. Is there?
I don't any problem here. I think enforcing quotes for strings is a
good thing. If the config parser find unquoted strings, it should
generate an error and fail to parse the config.
Meanwhile I'll have a look at the reload bug and
schedule it for
the next release. Sorry for the inconvenience, I'll send you a
patch as soon as I know more.
Ok, thanks :) I don't think there's any urgency in fixing it, because
this bug is only triggered in the rare case of reconfiguring and
changing the NSID. Usually, the NSID, once set, is static. In our
case, it will even be just "nsid on;". So a fix in the next minor
release will be fine.
Regards,
Anand
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools -
http://gpgtools.org
Comment: Using GnuPG with Thunderbird -
http://www.enigmail.net/
iEYEARECAAYFAlIBFw8ACgkQi+U8Q0SwlCsrJQCffI09uIar1nhskrnF7leG7VjU
nSUAmweFjR2sAd+OrZAdMKKJLi3MEJrA
=2cdj
-----END PGP SIGNATURE-----