> Even if this > support were to be added, one would have to think about how to > maintain the sanity of such notifications--the daemon could say one > thing (incorrectly or maliciously), but the VFS could say another > thing. Besides, the daemon saying something like "file deleted" has > other repercussions if the kernel thinks the file exists and is in > use.
Might it be possible to have interfaces in libfuse like: static int fuse_push_unlink(const char* path); When a file system daemon called "fuse_push_unlink(path)" it would essentially be saying that it wants the state of the world to be as if it had received a .unlink callback with (path) as its argument and had returned success. libfuse would return failure on fuse_push_* calls if the VFS layer, which would be responsible for ensuring consistency, reports that such an operation is not possible (such as the file in question being in use). Does this make sense? Hamish --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
