On Wed, 9 Aug 2000, Scott G. Miller wrote: > > > > * Rename .freenetrc to $HOME/.freenet/node.properties > > > > * Give the client a configuration file also, called > > $HOME/.freenet/client.properties > > > > * We could put everything else in this directory also. I'm sure you guys > > all have opinions about this stuff, so let's have 'em. > You really can't get away with the above changes, since $HOME is a unix > specific feature and Freenet is supposed to be cross platform. > > > * Give the node daemon a configuration interface which piggy-backs on the > > socket the node is already listening on. Currently I will reject any > > connections that are not from localhost, but later we can think about > > remote administration (+authentication). Configuration is written/read by > > running node from $HOME/.freenet/node.properties.
> This is just a bad idea. Please do not allow remote configuration. Its > never necessary to change the configuration of a running node anyway. <CAREFULLY> It isn't? It was for me recently. Some other node was uploading a file that was growing and growing until it nearly filled up the allocated disk space. I tried kill -HUP after making the disk space for .freenet larger in .freenetrc. No go in Java it seems. </CAREFULLY> -- Marc Schneiders ------- Venster - http://www.venster.nl marc at venster.nl - marc at bijt.net - marc at schneiders.org _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
