Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#598 closed defect (invalid)

Starting from init.d seems to ignore TAHOEHOME in /etc/default/tahoe-lafs

Reported by: amontero Owned by:
Priority: minor Milestone:
Component: other Version:
Keywords: Cc:
Parent Tickets: Sensitive: no

Description

I have a node and an introducer running on my Ubuntu Lucid.
I configure run-as-daemon the user in /etc/default/tahoe-lafs .
If my autostarting node lives in ~/.tahoe (or if I symlink it) everything works OK.

However, if I configure TAHOEHOME to another dir, tahoe fails to start. When invoking "sudo /etc/init.d/tahoe-lafs start", I get the following output:

* Starting Tahoe-LAFS tahoe

'/home/amontero/.tahoe' does not look like a directory at all

I tried absolute and relative paths and it makes no difference. The error message makes me think that tahoe is ingnoring the TAHOEHOME setting.

I'm using the i2p ppa tahoe 1.8.3 version.
Can anybody confirm if this is really a bug or some misunderstanding of mine?

Note: this bug report is actually a repost of main tahoe-lafs trac. You might be interested also in looking it at https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1661

Thanks.

Subtickets

Change History (2)

comment:1 Changed 8 years ago by DISABLED

Milestone: 0.8.13
Resolution: invalid
Status: newclosed
Version: 0.8.12

Yes, there's a problem with the initscript. A fixed package has been uploaded and should be built by the launchpad build-daemons soon. In the meantime a fixed initscript can be obtained from http://pastethis.i2p/show/T3ljXa0nZtQF9rcCMZkj/ and a fixed package is available at http://killyourtv.i2p/debian/pool/main/t/tahoe-lafs/

(closing as invalid since problems with my unofficial packages don't belong in the I2P project's bug tracker).

comment:2 Changed 8 years ago by amontero

Thanks kytv.
Where should I report them? I looked first in Launchpad but I could not post new bugs.

Note: See TracTickets for help on using tickets.