[tahoe-dev] tips on debugging Tahoe-LAFS client

Rohit Mehta pigdog at gmail.com
Wed Apr 17 02:26:46 UTC 2013


Hi everyone, I guess what I am looking for is already a ticket daira is
working on (as listed here:
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1489)  I think the ability to
use the Python shell to inspect objects at a point would be great to help
new people (like me) to get familiar with this code.  For the interim,
logging/file-output seems to work.

I have been able to make some very hacky additions to Tahoe-LAFS so far,
including adding a working getxattr and listxattr method to pyfilesystem
and dummy (nonworking) delxattr and setxattr method.

I also went into web/filenode.py and added a dummy xattr dict
(xattr['attr1']=1, xattr['attr2']=1) and verified that getxattr works
correctly if every file has these two extended attributes.  As far as an
actual implementation, The way I'm thinking now, I should try to store a
database of xattrs associated with URI:SSK  on the client (possibly in
~/.tahoe/private/xattr-database.txt).  I am not really sure if this should
be stored on the storage nodes, but for now storing this additional
information on the client seems a lot more straightforward (especially
since I want to try to use it to guide convergent encryption policies)

Rohit





On Sat, Apr 13, 2013 at 2:20 PM, Rohit Mehta <pigdog at gmail.com> wrote:

>
> Hi everybody, I've been playing with the code in the Tahoe-LAFS client and
> pyfilesystem and have been having some difficulties debugging.  I'm pretty
> much done with pyfilesystem and all my work is with the tahoe-lafs source
> files now.  I am very new to python, so I apologize if my questions are
> newbish.
>
> In filenode.py, I was able to get debugging information by using
> log.msg(...level=log.UNUSUAL)
>
> And in other files, in order to get additional information I've been doing
> hacky things like
> os.system("echo .... >>/tmp/mylog.log")
>
> Is there a better way to go about doing this?  I can connect to manhole
> ssh server, but I'm not certain how to get information about the running
> tahoe python process.
>
> Thanks in advance for any assistance,
>
> Rohit
> --
>



-- 
--------------------------------------------------------------------------

                      ,'``.._   ,'``.
                     :,--._:)\,:,._,.:       All Glory to
                     :`--,''   :`...';\      the HYPNO TOAD!
                      `,'       `---'  `.    http://youtu.be/zHU2RlSCdxU
                      /                 :
                     /                   \
                   ,'                     :\.___,-.
                  `...,---'``````-..._    |:       \
                    (                 )   ;:    )   \  _,-.
                     `.              (   //          `'    \
                      :               `.//  )      )     , ;
                    ,-|`.            _,'/       )    ) ,' ,'
                   (  :`.`-..____..=:.-':     .     _,' ,'
                    `,'\ ``--....-)='    `._,  \  ,') _ '``._
                 _.-/ _ `.       (_)      /     )' ; / \ \`-.'
                `--(   `-:`.     `' ___..'  _,-'   |/   `.)
                    `-. `.`.``-----``--,  .'
                      |/`.\`'        ,','); SSt
                          `         (/  (/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20130416/388d6db4/attachment.html>


More information about the tahoe-dev mailing list