Description of problem: This RFE is to track the changes required in the fuse-bridge to generate the events to be consumed by the eventing framework. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
The log messages in the gluster fuse code (namely fuse-bridge.c,fuse-resolve.c and fuse-helpers.c) are mostly related to inode/fd resolution and invalidation. These are not particularly useful to the admin/ user from a asynchronous event notification point of view, Syscalls made by the application would anyway receive an errno when the FOP fails. As there are no user-relevant messages at the moment that are possible candidates for consumption by the eventing framework , I am closing the BZ for now.