From: Zooko O'Whielacronx <zooko@zooko.com>
Date: Thu, 24 Dec 2009 22:35:22 +0000 (-0800)
Subject: docs: fix helper.txt to describe new config style
X-Git-Tag: trac-4200~66
X-Git-Url: https://git.rkrishnan.org/architecture.txt?a=commitdiff_plain;h=47003fdc0736fc7324b5b14395b0b8bd856d4e3a;p=tahoe-lafs%2Ftahoe-lafs.git

docs: fix helper.txt to describe new config style
---

diff --git a/docs/architecture.txt b/docs/architecture.txt
index fc2e67c5..5119f442 100644
--- a/docs/architecture.txt
+++ b/docs/architecture.txt
@@ -1,5 +1,7 @@
 
-   Allmydata "Tahoe" Architecture
+   Tahoe-LAFS Architecture
+
+(See the docs/specifications directory for more details.)
 
 OVERVIEW
 
diff --git a/docs/helper.txt b/docs/helper.txt
index 3be57960..b78f7742 100644
--- a/docs/helper.txt
+++ b/docs/helper.txt
@@ -65,10 +65,10 @@ What sorts of machines are good candidates for running a helper?
    much free disk space as there will be simultaneous uploads. When an upload
    is interrupted, that space will be used for a longer period of time.
 
-To turn a Tahoe client node into a helper (i.e. to run a helper service in
-addition to whatever else that node is doing), just create a file in your
-node's base directory named "run_helper", and put any non-empty string in it.
-Then restart the node:
+To turn a Tahoe-LAFS node into a helper (i.e. to run a helper service in
+addition to whatever else that node is doing), edit the tahoe.cfg file in your
+node's base directory and set "enabled = true" in the section named 
+"[helper]". Then restart the node:
 
  echo "yes" >$BASEDIR/run_helper
  tahoe restart $BASEDIR