[tahoe-lafs-trac-stream] [tahoe-lafs] #2045: Make the paths of the different folders configurable

[tahoe-lafs]

#2045: Make the paths of the different folders configurable
-------------------------+-------------------------------------------------
     Reporter:  meskio   |      Owner:  daira
         Type:           |     Status:  assigned
  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:20 leif]:
 > A few notes:
 > * `test_log_dir` needs to be updated for the change from `logdir` to
 `incident_dir`

 Ack.

 > * the name `incidents_dir` (plural) might be better

 Are there several directories to store a node incident logs?

 > * perhaps `storedir` should be `storage_dir`? I think whole words and
 underscores are preferable. s/tempdir/temp_dir/ too.

 Ack, that makes sense.

 > * as meskio and I discussed yesterday at 30c3, it does not seem like it
 would be trivial to make `tahoe.cfg` able to configure the path to
 twistd.log because that path is needed in `scripts/startstop_node.py` when
 the config file has not yet been read. A simple solution for properly
 debianizing tahoe is to just have the `--logdir` option passed on the
 commandline by the init script, perhaps configured in `/etc/default/tahoe-
 lafs` or something like that. (The pull request includes a `--logdir`
 commandline option, not to be confused with the `incident_dir` config
 option which was previously called `logdir`.)

 That is the conclusion meskio and I also ended on. I'm willing to
 implement this in the Debian initscript as soon as the patches are
 accepted.

 > * the `--logdir` option needs to be documented

 Ack.

 > * maybe the `--logdir` option should actually be `--logfile` (as the
 twistd option derived from it is) so that the log file doesn't have to be
 called twistd.log. That way it could log to something like `/var/log
 /tahoe-lafs.log`."

 In case sysadmins run a lot of nodes, this might be a bit confusing, or
 hard to dig in a one-log-file-rules-them-all. Having one logfile per node
 would probably be much more useable in this regard. That would also
 require more code change to maintain backward compatibility, as the
 `twistd.log` filename is appended to the logdir option at the moment. But
 I admit I'm unsure about this, maybe I missed something.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2045#comment:21>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage