Changes between Version 2 and Version 3 of Ticket #2324, comment 1
- Timestamp:
- 2014-10-25T02:59:56Z (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #2324, comment 1
v2 v3 1 1 Aliases are read from the node directory in effect for the CLI command, which can be different from the base directory of the gateway. By default, this will be `~\.tahoe`, which explains the behaviour you saw. Remember that the CLI command is not *in general* running with access to the same filesystem hierarchy as the gateway, so it wouldn't be correct for it to take the gateway's base directory as its default node directory. 2 2 3 To fix this, use `tahoe --node-directory=c:\asr\.tahoe check tahoe:` (this syntax assumes Tahoe-LAFS v1.10.0 or later). Alternatively you can make `~ /.tahoe/private` contain the intended default `aliases` file.3 To fix this, use `tahoe --node-directory=c:\asr\.tahoe check tahoe:` (this syntax assumes Tahoe-LAFS v1.10.0 or later). Alternatively you can make `~\.tahoe\private` contain the intended default `aliases` file. 4 4 5 5 Is there any way we could have made this clearer in the docs?
