Yes, this is known behavior. It should happen regardless of whether you are using Objective-C or not. I have looked at it in the past, and on the face of it, it's signal related. It could be a bug--either in the MacFUSE user-space library or in Mac OS X. I haven't had time to look at it after that, but it's on my TODO list.
Until then, you have to work it around somehow. Amit On Feb 20, 11:32 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > I have been playing with some basic code that watches for specific > connect/disconnect events and then mounts/unmounts a fuse volume using > the macfuse obj-c framework. (on Leopard) > > Unfortunately no matter what I do I always get the error > "the MacFUSE file system is not available (-1)" > whenever I call mountAtPath for a second time to remount the volume > after a disconnect/connect cycle has occured. > > As best I can tell this appears to be related to the kmodload function > in the macfuse patches, but I haven't explored exactly how. > > Any help would be much appreciated. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "macfuse-devel" 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-devel?hl=en -~----------~----~----~----~------~----~------~--~---
