Can you provide more details? For example: * Sounds like your file system is NOT using MacFUSE.framework (Objective-C bindings to MacFUSE); is that correct?
* Which specific requests (read/write/getattr etc.) can block in your file system? Which type of objects can they block for: just files, or directories too? * How are you accessing the file system when it gets stuck: through the command line or through the Finder? * When the whole thing gets stuck, does it get unstuck when the blocking request unblocks? On Aug 25, 6:49 pm, Daniel Benamy <[EMAIL PROTECTED]> wrote: > I've got a fuse file system which sometimes intentionally blocks > requests. It works with fuse on linux which spawns new threads for > each request and is happy to leave some hanging around for a while and > process other requests. But when I run it with macfuse, its acting as > though when one request blocks, the whole thing gets stuck. Is this > intentional? Is there any way around it? I did a bit of searching on > the web and skimmed the code and I haven't found anything about 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 -~----------~----~----~----~------~----~------~--~---
