Not sure what the 'subject' actually means... in what way does it not 'work'? Basically NodeConfig.exe assumes the node knows what parameters are handled. The trick here is that the Config module is invoked to generate a dummy conf file and then the parameters generated by NodeConfig are filtered INTO this file. If a setting is not present in the dummy conf file immediately before invoking NodeConfig, then it won't be present in the conf file immediately after invoking NodeConfig. If you find 'unhandled config params' the easiest solution is to load NodeConfig, change nothing, and save your new settings. The node's dummy conf will be filled in with your real settings and unhandled config params will be magically lost.
That's the theory, anyway. What is it you're doing/seeing? d ----- Original Message ----- From: "Ian Clarke" <i...@locut.us> To: <devl at freenetproject.org> Sent: Monday, March 24, 2003 8:43 PM Subject: [freenet-dev] deleting unhandled config params doesn't work in NodeConfig.exe _______________________________________________ devl mailing list devl at freenetproject.org http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
