[tahoe-lafs-trac-stream] [tahoe-lafs] #1936: the tahoe-lafs logging system is hard to discover

[tahoe-lafs]

#1936: the tahoe-lafs logging system is hard to discover
------------------------------+--------------------------------------------
     Reporter:  zooko         |      Owner:
         Type:  defect        |     Status:  new
     Priority:  normal        |  Milestone:  undecided
    Component:  code-         |    Version:  1.9.2
  nodeadmin                   |   Keywords:  usability transparency logging
   Resolution:                |
Launchpad Bug:                |
------------------------------+--------------------------------------------

Comment (by warner):

 Replying to [comment:4 zooko]:

 > For that matter, what about the major strategy change of not
 > implementing daemonization ourselves at all! We could leave that
 > job up to daemontools, supervisord, upstart, systemd, or {{{tahoe
 > run > tahoe-stdout.log.txt 2> tahoe-stderr.log.txt &}}}.

 I dunno. Daemonizing a tahoe node is a very common thing for people
 to do. Twisted has excellent built-in daemonization tools. I don't
 want to ask users to discover and learn some external daemonization
 tool before they're able to do a very common operation. And my own
 test/deployment workflow would be a lot harder if I had to use
 daemontools just to launch a half-dozen local nodes. I still miss
 tahoe's built-in {{{--multiple}}} feature. So I'm -1 on removing
 this functionality from tahoe.

 Incidentally, that {{{tahoe run >logs &}}} command doesn't record a
 PID anywhere (making it hard to kill, especially when you run
 multiple nodes), doesn't necessarily detach from the terminal (so
 logging out might kill the process), doesn't rotate the logfiles,
 throws any init-time errors into the stderr logfile where they
 won't be noticed, and has no way to report setup/config errors via
 an exit status code. All things that {{{tahoe start}}} provides :).

 OS packagers, on the other hand, will have some preferred
 daemonization solution in mind already, so the non-daemonizing
 {{{tahoe run}}} is important to maintain for them to use.

 > Also, what do you think about [comment:1 the earlier proposal] to
 > have {{{tahoe --help}}} mention the existence of the
 > [source:docs/logging.rst] file?

 It's not a bad idea, although I worry that {{{tahoe --help}}} is
 too long (61 lines at the moment). Once it grows beyond a page, it
 becomes hard to use. But one more line might be ok.

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