From: Brian Warner Date: Tue, 5 Feb 2008 21:33:29 +0000 (-0700) Subject: docs/configuration.txt: document nickname, no_storage, readonly_storage X-Git-Tag: allmydata-tahoe-0.8.0~153 X-Git-Url: https://git.rkrishnan.org/specifications/banana.xhtml?a=commitdiff_plain;h=d35b2f304fff9fc3c16e749b9b6ac089f49dbb30;p=tahoe-lafs%2Ftahoe-lafs.git docs/configuration.txt: document nickname, no_storage, readonly_storage --- diff --git a/docs/configuration.txt b/docs/configuration.txt index 74b298fc..4ea28e2e 100644 --- a/docs/configuration.txt +++ b/docs/configuration.txt @@ -20,6 +20,10 @@ furl is created by the introducer node and written into its base directory when it starts, whereupon it should be published to everyone who wishes to attach a client to that grid +nickname (optional): The contents of this file will be displayed in +management tools as this node's "nickname". If the file doesn't exist, the +nickname will be set to "". + webport (optional): This controls where the client's webserver should listen, providing filesystem access as defined in webapi.txt . This file contains a Twisted "strports" specification (as defined in @@ -55,6 +59,17 @@ for debugging. To cause the node to accept SSH connections on port 8022, symlink "authorized_keys.8022" to your ~/.ssh/authorized_keys file, and it will accept the same keys as the rest of your account. +no_storage (optional): If this file is present (the contents do not matter), +the node will not run a storage server, meaning that no shares will be stored +on this node. Use this for clients who do not wish to provide storage +service. + +readonly_storage (optional): If this file is present (the contents do not +matter), the node will run a storage server but will not accept any shares, +making it effectively read-only. Use this for storage servers which are being +decommissioned: the storage/ directory could be mounted read-only, while +shares are moved to other servers. + sizelimit (optional): If present, this file establishes an upper bound (in bytes) on the amount of storage consumed by share data (data that your node holds on behalf of clients that are uploading files to the grid). To avoid