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...
D. On Apr 19, 1:16 am, Anatol Pomozov <[email protected]> wrote: > I am trying to port tup build tool (http://gittup.org/tup/) to macosx. > > Tup (one of the experimental branches) utilizes fuse. Tup creates a > filesystem using fuse_mount/fuse_new/fuse_loop. Here is the code that works > fine on > Linuxhttps://github.com/anatol/tup/blob/fuse/src/tup/server/fuse_server.c > > I am trying to run it on macosx 10.6.7 with macfuse from macports and it > fails. All functions (fuse_mount/fuse_new/fuse_loop) return non-errors, but > later when I try to "cd" into filesystem that was just created fuse crashes > > Users/anatol/sources/tup: No such file or directory > mount_fusefs: failed to mount /Users/anatol/sources/tup/.tup/mnt@/dev/fuse0: > Socket is not connected > > Here is a log from dmesg: > MacFUSE: force ejecting (no response from user space 5) > MacFUSE: user-space initialization failed (57) > > I can't find any answer in faq/maillist. Could you help me to resolve this > issue? -- 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.
