id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	launchpad_bug
1661	Starting from init.d seems to ignore TAHOEHOME in /etc/default/tahoe-lafs	amontero	nobody	"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?

Thanks."	defect	closed	minor		contrib		invalid	i2p	killyourtv@…