Yes, you really ought to read all the documentation (at least the FAQ and the OPTIONS documents).
MacFUSE does have almost the same developer-visible API as Linux FUSE, but its kernel implementation is entirely different and OS X-specific. It has to be: Mac OS X VFS is nothing like Linux VFS either. Therefore, if you are coming from Linux and are used to the Linux implementation of FUSE, the best way to avoid being surprised piece-by- piece is to read up all you can one shot. Amit On Aug 26, 10:06 pm, "ted bonkenburg" <[EMAIL PROTECTED]> wrote: > See the "daemon_timeout" option: > > http://code.google.com/p/macfuse/wiki/OPTIONS > > I suspect this will explain what is going on. > > ted > > On Tue, Aug 26, 2008 at 9:50 PM, Daniel Benamy <[EMAIL PROTECTED]> wrote: > > > I've got an odd problem. If I run my file system and use some > > operations including open and readlink, it's fine. If I use my read > > which is a special blocking call, it seems to works ok for maybe a > > minute and the suddenly the file system closes. gdb says it's exiting > > normally and I've run it with libgmalloc and it's not accessing > > invalid memory. If I do the read and then nothing else it'll close > > after a little while and if I do other things after the read (while > > it's still blocked) they work until it exits. Any ideas about what > > could cause this? > > Thanks a lot, > > Dan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "macfuse-devel" group. To post to this group, send email to macfuse-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/macfuse-devel?hl=en -~----------~----~----~----~------~----~------~--~---
