When you run start-freenet.sh (latest snapshot) without a freenet.conf (which I did to try and find out what the developers thought should and shouldn't be in freenet.conf at the moment) you get to a "list of services which are run when the node starts". You are invited to type in fproxy. If you do so, freenet.conf is generated with just fproxy as a service, not "mainport" or "nodestatus", which are the defaults. This is consistent, but unhelpful if mainport or nodestatus entries are still needed. -- Roger Hayter
_______________________________________________ devl mailing list devl at freenetproject.org http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/devl
