Hi, I'm running a freenet node on my Linux server, and currently it automatically (crontab+script) checks to see if a new freenet-latest.jar is available, and if so, updates&restarts freenet. However, I read on the Freenetproject website that it is recommended for large nodes to wait some time before updating. It would be no problem to let the script download an update, and wait some before actually updating freenet with it, but the problem is that I have no idea what delay would be optimal for my node. Can anyone give me a clue? My datastore is currently 5 GB, I plan to change the limit to 10 GB in the near future. Upstream bandwidth is limited to 10 kb/sec (by Linux HTB qdiscs, since the built-in limit doesn't work very well for me; see http://www.lartc.org if you're interested). Downstream is max. 50 kb/sec.
Also, how bad is it for freenet when a node restarts? On my Celeron 366 server Freenet takes at least 5 minutes to fully restart, will neighbouring nodes that fail to contact my node during that time just decide to give up and forget about it? By the way, I just had some problems subscribing to this list; it seems that the subscribe page on hawk.freenetproject.org is served from port 8080, but the form on that page tries to send its contents back to port 80. (I subscribed by downloading the subscribe page and adding :8080 to the url that the form submits to) Arjen _______________________________________________ support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support
