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

 This problem is compounded by the fact that there exists a
 {{{~/.tahoe/logs}}} directory which looks at first glance like it has all
 the logs in it. This means people will assume that they've seen the logs
 after looking in there, and if they don't see any error messages in there
 then there aren't any error message being logged. An example of this
 (probably) just happened:

 {{{
 <dash> hmm. anyone tried bzr with tahoe-lafs over sftp recently?   [10:01]
 <dash> getting errors about "readv() returned 0 bytes"  [10:02]
 <zooko> dash: hm. I have not.
 <zooko> This is... bzr talking to the tahoe-lafs SFTP interface?  [10:28]
 <zooko> dash: do you know how to loo for tahoe-lafs logs?
 <dash> sure, in ~/.tahoe/logs
 }}}

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