Re: FSEvents in Kernel Extension
Re: FSEvents in Kernel Extension
- Subject: Re: FSEvents in Kernel Extension
- From: Mike Mackovitch <email@hidden>
- Date: Tue, 14 Oct 2014 09:40:39 -0700
On Tue, Oct 14, 2014 at 06:11:46PM +0200, Charles Francoise wrote:
>
> Yes, I was referring to the NFS server.
> Our filesystem also has a network component and I would like to generate FSEvents for events originating in the network.
>
> As you say, the FSEvents interface is private. I wish it was part of the kpi.
Wishing might help... but telling Apple officially is usually more effective: https://bugreport.apple.com/
FWIW, I think getting VNOP_MONITOR/vnode_notify made public is more likely to
happen than getting access to the VFS fsevents API.
On Tue, Oct 14, 2014 at 11:16:24AM -0500, Paul Nelson wrote:
>
> On Oct 14, 2014, at 10:51 AM, Mike Mackovitch <email@hidden> wrote:
> > I was going to point you in the direction of VNOP_MONITOR/vnode_notify
> > which is used by the NFS client file system to report events on monitored
> > vnodes; but alas, that also appears to be private.
>
> I filed a bug report on this on Oct 8, 2010 (four years ago). I marked it a high priority because we use this in our DAVE and ADmitMac products.
>
> For some reason this bug is closed. The bug number is
> 8509887.
Hmm. It looks like that may have been erroneously closed when more
information was requested. If you're still interested in having it
addressed, I would suggest requesting that it be reopened - and, if
it doesn't get reopened, filing another request.
HTH
--macko
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Filesystem-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden