[tahoe-lafs-trac-stream] [tahoe-lafs] #2045: Make the paths of the different folders configurable
tahoe-lafs
trac at tahoe-lafs.org
Tue Dec 3 12:23:09 UTC 2013
#2045: Make the paths of the different folders configurable
--------------------------------+------------------------------------
Reporter: meskio | Owner: daira
Type: enhancement | Status: new
Priority: normal | Milestone: undecided
Component: code-nodeadmin | Version: 1.10.0
Resolution: | Keywords: FHS unix daemon twistd
Launchpad Bug: |
--------------------------------+------------------------------------
Comment (by bertagaz):
Thanks for the #1310 pointer. These two issues certainly share commons.
I've taken time to think and read more the code regarging this FHS issue.
Sure the way tahoe is made isn't really fiting to the proposed changes
regarding configuration files.
But maybe that's because once they are removed from basedir, there's
almost nothing left in there when meskio's patches have been applied.
Well, appart three things i've seen, maybe more as I surely have missed
some:
* `tmp/`:
This one was fine to lay in basedir if this directory was under /var/
* `tmpfile`:
Same as previous
* `picklefile`:
Stats_gatherer data
So, another approach for tahoe-lafs to be FHS compliant in vendors would
be to make basedir being a subdir of `/etc/tahoe-lafs/` rather than
`/var/lib/tahoe-lafs/`.
Then the two tmp contents should probably be in a subdir of `/var/tmp
/tahoe-lafs/`. Regading the picklefile, a subdir of `/var/lib/tahoe-lafs/`
might be the right place.
In the end, this approach would require very little changes to add in
meskio's patches, and not so much in Debian's packaging too.
Does it sound realistic? More interesting regarding support burden? Any
other stuff that should get out of basedir once considered as a
configuration directory?
--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2045#comment:11>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage
More information about the tahoe-lafs-trac-stream
mailing list