[tahoe-dev] tahoe_fuse: Add simple file-based logging.

[Nathan]

Thanks for the feedback.

The python-fuse library appears to support many commandline options,
but I have not been able to cause any of them except "-ho" to work.
If I pass "-ho" on the commandline, I see a bunch of options help, and
then an exception.

Maybe some combination of these would work on your system.  You
mentioned that you got gmailfs working, correct?  Maybe I should view
the source to that for comparison.

Nathan

On Jan 19, 2008 8:18 PM, Peter Secor <secorp at secorp.net> wrote:
> Also note that I did this both as root and as a user.
>
> Ps
>
>
> Peter Secor wrote:
> > Hi Nathan,
> >
> >   I just tried out the latest on my mac and here's what it gives:
> >
> > peter-secors-computer:~ secorp$ python
> > trees/tahoe-trunk/contrib/fuse/tahoe_fuse.py tahoefs
> > kextload: /Library/Filesystems/fusefs.fs/Support/fusefs.kext loaded
> > successfully
> > peter-secors-computer:~ secorp$ mount
> > /dev/disk0s2 on / (hfs, local, journaled)
> > devfs on /dev (devfs, local)
> > fdesc on /dev (fdesc, union)
> > map -hosts on /net (autofs, automounted)
> > map auto_home on /home (autofs, automounted)
> > /dev/disk1s2 on /Volumes/secorp (hfs, local, nodev, nosuid, journaled,
> > noowners, mounted by secorp)
> > Python at fuse0 on /Users/secorp/tahoefs (fusefs, nodev, nosuid,
> > synchronous, mounted by secorp)
> > peter-secors-computer:~ secorp$ ls tahoefs/
> > ls: : Device not configured
> >
> >   Note that there is a logfile now in the .tahoe/logs directory, but it
> > only outputs:
> >
> > peter-secors-computer:~ secorp$ cat .tahoe/logs/tahoe_fuse.log
> > Log opened at: 2008-01-19 20:05:35
> > Initializing with confdir = '/Users/secorp/.tahoe'
> > peter-secors-computer:~ secorp$
> >
> >   I'll poke around and see if I can't get some more log messages
> > printing out to see what the device needs in order to be "configured".
> >
> > Ps
> >
> > Nathan wrote:
> >> Sorry folks, the previous patch depended yet again on this persistent
> >> viral patch which should *not* be in your repo:
> >>
> >> Tue Jan  8 10:28:16 PST 2008  zooko at zooko.com
> >>   tagged allmydata-tahoe-0.7.0
> >>
> >> This new attachment should not depend on that tag, which is hopefully
> >> finally truly obliterated from my repo and trunk.
> >>
> >> Nejucomo
> >>
> >>
> >>
> >>
> >> On Jan 19, 2008 1:41 PM, Nathan <nejucomo at gmail.com> wrote:
> >>> The more recent python-fuse library (which ubuntu calls 1:0.2-pre3-3)
> >>> forks to the background by default, and obscures the standard output.
> >>> The main patch in this send changes all of the output to go to
> >>> ~/.tahoe/logs/tahoe_fuse.log.
> >>>
> >>> I am now able to mount a directory (whose cap is stored in
> >>> ~/.tahoe/private/root_dir.cap) and run "find mountpoint -exec ls -ld
> >>> '{}' \;" with believable output.
> >>>
> >>> Regards,
> >>> Nathan
> >>>
> >>
> >>
> >> ------------------------------------------------------------------------
> >>
> >> _______________________________________________
> >> tahoe-dev mailing list
> >> tahoe-dev at allmydata.org
> >> http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev
> >
>