wigwam not up to date?
Roger
15 November 2009, 20:34
Hi,
I set BanOnSQLie = 30 in hiawatha.conf (recognize the "e" at the end).
Wigwam says "No critical errors detected" (or similar) but Hiawatha didnt start up. I would have assumed Hiawatha would start up at least with a warning and use the default value for BanOnSQLi or wigwam should have said "Wrong setting in line X".
Am I wrong?
Thanks for your great work Hugo!!
Hiawatha version: 6.17
Operating System: FreeBSD
Hugo Leisink
15 November 2009, 20:41
Wigwam probably said "No non-fatal errors found in the Hiawatha configuration.". All fatal checks are done in Hiawatha. Wigwam only checks for several non-fatal ones. Having BanOnSQLie in your confguration file is a fatal error and therefor checked by Hiawatha, not by Wigwam.
Wigwam checks for several errors which Hiawatha can't detect, because of a different way of reading the configuration file. Of course I could include those checks in Hiawatha, but that would have made the Hiawatha binary bigger. Since that code is only used during startup, I made a separate binary.
This topic has been closed.