On Sun, Jan 26, 2003 at 09:20:27PM +0100, Arjen Meek wrote:
> 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.
It is very rare that an update will cause your node to completely stop
working at the node side and become useless to freenet. We have had a
few problems with the web interface in recent updates.
> 
> 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?
Not exactly, but it's no big deal if it's only once a day.
> 
> 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)
I have been told that people are working on it... we do need to fix it
before the 0.5.1 release.
> 
> Arjen

-- 
Matthew Toseland
[EMAIL PROTECTED][EMAIL PROTECTED]
Full time freenet hacker.
http://freenetproject.org/
Freenet Distribution Node (temporary) at http://amphibian.dyndns.org:8889/x2d5tv0Ymqo/
ICTHUS.

Attachment: msg02714/pgp00000.pgp
Description: PGP signature

Reply via email to