tahoe-lafs/tahoe-lafs
tahoe-lafs
/
tahoe-lafs
2
0
Fork 0
Code Issues Pull Requests 23 Packages Projects Releases 1 Wiki Activity

docs/configuration.txt: explain the current limitations of readonly_storage

This commit is contained in:
Brian Warner 2008-06-03 17:47:08 -07:00
parent 0aa6d24d62
commit 699d912d80
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/configuration.txt
View File

@ -71,7 +71,9 @@ 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, 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 making it effectively read-only. Use this for storage servers which are being
decommissioned: the storage/ directory could be mounted read-only, while decommissioned: the storage/ directory could be mounted read-only, while
shares are moved to other servers. shares are moved to other servers. Note that this currently only affects
immutable shares. Mutable shares (used for directories) will be written and
modified anyway. See ticket #390 for the current status of this bug.
sizelimit (optional): If present, this file establishes an upper bound (in 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 bytes) on the amount of storage consumed by share data (data that your node