I coded that up a bit ago mainly for changing logLevel on the fly. It also currently supports aggressiveGC and configUpdateInterval. With the way Fred's config is setup there is no fixed place in memory to change an option to update it. Every option needs to be updated in a different place, many of them in multiple places. For this reason an individual method needs to be written to handle each config option. The handlers go in:
src\freenet\node\NodeConfigUpdater.java Currently its main purpose is so people having problems with Fred can change their logLevel to debug, without restarting, to get a log file a developer can look at to find and fix the problem. It works by checking the timestamps of the config files at startup and at each checkpoint checking to see if they have changed. If they have, the config is read in, compared to the config previously read in, and 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. -Pascal On Tue, 25 Feb 2003 19:49:25 -0000, Dave Hooper wrote: > >> It checks for changes and then will change the node's config on the fly >> (without restart it) > >I'd guessed that bit ... :-) > >> but I've tried and get an error like: >> value changed but no handler was available >> so I think: no, it doesn't work... maybe a bug. > >Anyone have any success? What about its author - is it a final feature >which only works for a select few config parameters (if so, which ones), or >is it a disabled-work-in-progress? > >d _______________________________________________ devl mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
