[tahoe-dev] Debian packages?
Greg Troxel
gdt at ir.bbn.com
Wed Apr 20 05:21:15 PDT 2011
Olivier Schwander <olivier.schwander at chadok.info> writes:
> Yes, you may run multiple tahoe instances using different user id but I
> think it's still a good idea to provide a system wide installation, with
> a specific user and specific data and config dirs (if you look at apache
> for example, you are still able to run your own custom apache with a
> custom config, even if the package provide a system-wide configuration).
That's reasonable, but there should not be a system node unless
requested and set up.
I agree that it's also reasonable to have system config in /etc and data
someplace where data is expected to be (but it may be very large, so
typically one thinks about which disk and where there is space).
On my systems, I put nodes in /n[012]/TAHOES/gridname-hostname-diskname, and
run them under the 'tahoes' user (for tahoe server). To me, the node
config is minor and the data storage location is the real question.
But others may prefer FHS compliance to that.
So it sounds like there are 1, maybe two enhancement requests:
add a variable storage_dir= to the config to have the storage
directory be other than $node_dir/storage
very maybe, script support to start multiple tahoe nodes under
specific uids, maybe based on a /etc/tahoe-nodes.config global config
file that has uid/dir pairs. This is perhaps best added by
packagers, but I suspect it's easy enough to write in POSIX /bin/sh
and be portable to all Linux and BSD variants, at least, and maybe
more.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20110420/15c82b22/attachment.pgp>
More information about the tahoe-dev
mailing list