[tahoe-lafs-trac-stream] [tahoe-lafs] #1310: If --node-url is present then --node-directory is mostly but not entirely ignored.
tahoe-lafs
trac at tahoe-lafs.org
Fri Jan 21 07:22:42 UTC 2011
#1310: If --node-url is present then --node-directory is mostly but not entirely
ignored.
-----------------------------------+----------------------------------------
Reporter: zooko | Owner: warner
Type: defect | Status: reopened
Priority: major | Milestone: undecided
Component: code-frontend-cli | Version: 1.8.1
Resolution: | Keywords: usability
Launchpad Bug: |
-----------------------------------+----------------------------------------
Comment (by mlakewood):
In addition to this i've experienced the following problem. If I create a
client node in the default directory ie .tahoe through tahoe create-client
command, and then modify the '''web.port = tcp:3457:interface=127.0.0.1'''
to be say '''web.port = tcp:3457:interface=10.0.10.89''' when you try to
run a command it will thow and exception about trying to connect to the
client. This is because in node.url its still pointing at
http://127.0.0.1:3457 . If you change this to point at 10.0.10.89:3457
then all is good. however if you stop and start the tahoe client then the
node.url is reset to http://127.0.0.1:3456 . which is a bit of a usability
problem.. node.url seems like a configuration file, but gets overridden
with a potentially invalid default. It seems to me node.url shouldn't be
overriden on tahoe start.
--
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1310#comment:4>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage
More information about the tahoe-lafs-trac-stream
mailing list