5tucatz elPunishar ([EMAIL PROTECTED]) wrote:

> additional to that, you _don't_ have to shut down your node to update.

Huh?

> just run the update script and when its done, restart your node. voila.

So you *do* have to restart the node, which is exactly the same thing
as shutting it down and then starting the new one.

Stopping a Freenet node aborts all active data transfers, and
starting it back up with a large data store can take a few minutes.

But I agree with Ian -- upgrades are not mandatory.  In many cases
they're not even advisable; I've avoided builds 538 and 539 because
of numerous reports of problems that were solved by reverting to 537.
In any event, I'd advise most permanent node operators to wait a
day or so before upgrading to a new build, just to avoid any brown
paper bag bugs.  I mean, do you upgrade to the latest "stable"
(haha) Linux kernel release the same day it comes out?  (If you're
a /.  drone, don't bother answering that. ;-) )

-- 
Greg Wooledge                  |   "Truth belongs to everybody."
[EMAIL PROTECTED]              |    - The Red Hot Chili Peppers
http://wooledge.org/~greg/     |

Attachment: msg02473/pgp00000.pgp
Description: PGP signature

Reply via email to