From: Brian Warner <warner@allmydata.com>
Date: Wed, 4 Jun 2008 00:47:08 +0000 (-0700)
Subject: docs/configuration.txt: explain the current limitations of readonly_storage
X-Git-Tag: allmydata-tahoe-1.1.0~49
X-Git-Url: https://git.rkrishnan.org/components/%22news.html/frontends/%22file:/vdrive?a=commitdiff_plain;h=699d912d80ceae1052a8025f5944de386e92094c;p=tahoe-lafs%2Ftahoe-lafs.git

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

diff --git a/docs/configuration.txt b/docs/configuration.txt
index f9d3b9b3..a7487a01 100644
--- a/docs/configuration.txt
+++ b/docs/configuration.txt
@@ -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,
 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.
+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
 bytes) on the amount of storage consumed by share data (data that your node