> I coded that up a bit ago mainly for changing logLevel on the fly. It > also currently supports aggressiveGC and configUpdateInterval. [...] > The handlers go in: > src\freenet\node\NodeConfigUpdater.java > [...] > the handlers for any changed options are called. If no handler has been > written for a changed option you get the error you've been seeing.
In which case could we please have an option that dumps to stdout, or a file, a list of the available handlers (by config parameter). That way control tools (I have in mind the NodeConfig app for Windows) can determine whether or not the node needs to be restarted for config changes to take place... IDEALLY something like: [Handlers] logLevel=yes mainport.Port=no ... that kind of thing (although just the 'yes' entries could be sufficient) d _______________________________________________ devl mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
