diff --git a/FAQ.md b/FAQ.md index efede53..a25f3b8 100644 --- a/FAQ.md +++ b/FAQ.md @@ -27,7 +27,7 @@ A: A: Yes. François Deppierraz contributes [a buildbot](http://tahoe-lafs.org/buildbot/builders/FranXois%20lenny-armv5tel) which shows that Tahoe-LAFS builds and all the unit tests pass on his Intel SS4000-E NAS box running under Debian Squeeze. Zandr Milewski [reported](http://tahoe-lafs.org/pipermail/tahoe-dev/2009-November/003157.html) that it took him only an hour to build, install, and test Tahoe-LAFS on a PogoPlug. -**Q6" Does Tahoe-LAFS work on Windows?** +**Q6: Does Tahoe-LAFS work on Windows?** A: Yes. Follow [the standard quickstart instructions](http://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/docs/quickstart.rst) to get Tahoe-LAFS running on Windows. (There was also an "Allmydata Windows client", but that is not actively maintained at the moment, and relied on some components that are not open-source.) @@ -120,7 +120,12 @@ A: Tahoe-LAFS is designed to be unobtrusive. First of all, it doesn't start at a The two minor exceptions are that the server periodically inspects all of the ciphertext that it is storing on behalf of clients. It is configured to do this "in the background", by doing it only for a second at a time and waiting for a few seconds in between each step. The intent is that this will not noticably impact other users of the same server. For all the details about when these background processes run and what they do, read the documentation in [storage/crawler.py](http://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/src/allmydata/storage/crawler.py?annotate=blame&rev=4164) and [storage/expirer.py](http://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/src/allmydata/storage/expirer.py?annotate=blame&rev=4329). -**Q19: What about revoking access to a file or directory?** + +**Q19: If a storage server dies and new one is installed, will Tahoe-LAFS automatically generate a new share of each file to store on the new one?** + +A: Not automatically (see also [#Q18_unobtrusive_software Q18]). There is a repair operation, but it starts only when the use triggers it, by clicking on the "repair" button on the web user interface or running the "tahoe check" command. You can, of course, execute the "tahoe check" command from a script. Kevin Reid posted [his cron script](http://tahoe-lafs.org/pipermail/tahoe-dev/2009-October/003012.html) with which he has configured his node to repair all files every night. + +**Q20: What about revoking access to a file or directory?** Please see these mailing list threads: * [Tahoe Access Control](http://tahoe-lafs.org/pipermail/tahoe-dev/2011-June/006387.html)