[tahoe-lafs-trac-stream] [tahoe-lafs] #2045: Make the paths of the different folders configurable
tahoe-lafs
trac at tahoe-lafs.org
Fri Jan 3 15:23:08 UTC 2014
#2045: Make the paths of the different folders configurable
-------------------------+-------------------------------------------------
Reporter: meskio | Owner: leif
Type: | Status: new
enhancement | Milestone: undecided
Priority: normal | Version: 1.10.0
Component: code- | Keywords: FHS unix daemon twistd review-
nodeadmin | needed
Resolution: |
Launchpad Bug: |
-------------------------+-------------------------------------------------
Comment (by bertagaz):
Replying to [comment:32 meskio]:
> Replying to [comment:31 bertagaz]:
> > Replying to [comment:28 meskio]:
> > > The remaining parts are:
> > >
> > > And after that we won't have any parameter in 'create-node' to set
the 'introducers_dir'. bertagaz, is this flag needed for the debian
packaging? Should we add a '--introducers_dir' to 'create-node'?
> >
> > Please correct me if I'm wrong, but as I understand it, introducers
don't store any data in their basedir, so I don't think we need to have a
specific option for them.
>
> I don't know where is my brain :( I wanted to write 'incidents_dir',
sorry.
Travels often have that effect :)
Actually you might be raising an interesting point in favor of keeping
logdir (which was the historical name in tahoe) rather than switching to
logfile, as incidents_dir is using the value of the first one if set to
compute its own value. That is how I understand it. Switching to logfile
might introduce more complexity into the patch (and probably elsewhere),
for not so much gain IMHO. I think the patches are quite good at the
moment.
So is the logfile switch (not so related to FHS btw) very much needed in
the end?
--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2045#comment:33>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage
More information about the tahoe-lafs-trac-stream
mailing list