From: "Travis Bemann" <[email protected]> >The only comment is that *is this really the proper way to do this*? >Should Freenet clients be able to restart the Freenet node at all, >especially on multiuser systems and such (yes, UNIX is multiuser). In >addition, if this is to get around some bug in Fred which forces one >to regularly restart it, I think that it is just not the Right Way to >do it. Why not spend the time you would have spent coding this to >actually do some debugging so that you won't have to restart the >Freenet node? And if you can't get that to work well, why not include >code in the Freenet node to automatically restart itself periodically >or when certain criteria are met?
I'm wanting a convenient client-driven restart mechanism, NOT to work around supposed node bugs (I just leave my node running, for weeks on end, and it works fine), but as support to the configurator I wrote - AFAIK there's no way to make a node pick up new config settings without restarting. For instance, I'd like to be able to change the bandwidth throttles from time to time. Alternately, if there's a way to make a node re-read the configs without restarting, that would be far better still. David _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl
