I have discovered a problem with linuxconf modules which may cause a lot of trouble in some cases. First problem is that some modules are not aware of all the options a configuration file can use, and may crash when parsing the configuration file(s) if you have edited it with hand (outside linuxconf). Even worse is that it seems that linuxconf get trouble using the modules listed after the one that crash, and changes done in following modules are not activated etc. In my case there was two modules crashing, apache (because of the new 1.3 include directive I think), and dhcpd. The symptoms was that the treemenu was never generated completly (only got a part of the "control" tree), and the firewall was never updated (it was the last in the module list). This was the only indication I could see that something was wrong, no messages from the modules affected. After I disabled the apache and dhcpd modules, everything was fine again. I don't know if a chrashing module may cause trouble for other modules in all cases, or if there are similar problems in other modules, but if you have trouble activating a configuration change it could be an idea to look for problems in other non-related modules also (or try to put critical modules on top of the module list to see if it helps). I also hope someone with understanding of the module API could investigate this problem. Thanks, Stein Vr�le --- You are currently subscribed to linuxconf as: [[email protected]] To unsubscribe, forward this message to [EMAIL PROTECTED]
