Hi
On Mon, Apr 18, 2011 at 10:33 PM, ivenhov <[email protected]> wrote:
> Hi
>
> This probably won't help/apply here but is there anything like
> foreground/background mode
> switch in tup? Maybe there is something (fork) that kills your
> filesystem threads...
I tried to enable fuse debugging [1] and found some more info. I'll
send a question in a separate thread.
[1] Actually the only non-obvious way to enable fuse debugging for
fuse_mount/new that I found is to construct commandline args array and
then parse it using fuse_parse_cmdline (facepalm). Here is the code:
char *argv[] = {"youprogramm", "-d", MOUNTPOINT_DIR};
struct fuse_args args = FUSE_ARGS_INIT(3, argv);
fuse_parse_cmdline(&args, NULL, NULL, NULL);
fuse_mount(MOUNTPOINT_DIR, &args);
Is there any better way to enable fuse debug log?
--
You received this message because you are subscribed to the Google Groups
"MacFUSE" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/macfuse?hl=en.
