[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 zooko):

 Replying to [comment:7 gdt]:
 > I don't think it's accurate to say "OS packagers will have a
 daemonization plan".  As a packager I expect daemons to be well behaved by
 themselves.  Having a pidfile written would be good.
 >
 > It would also be nice to have an easy way to use syslog.   I gather
 flogtool has advantages, but syslog is the standard approach.

 Would you want the complete, verbose logs sent to syslog? It is currently
 possible by running {{{flogtool tail ~/.tahoe/private/logport.furl |
 logger}}}. Is that the behavior you want?

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