Re: FSEvents in Kernel Extension
Re: FSEvents in Kernel Extension
- Subject: Re: FSEvents in Kernel Extension
- From: Charles Francoise <email@hidden>
- Date: Tue, 14 Oct 2014 18:11:46 +0200
Thanks.
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.
Chrales
On 14 Oct 2014, at 17:51, Mike Mackovitch <email@hidden> wrote:
> On Tue, Oct 14, 2014 at 11:28:41AM +0200, Charles Francoise wrote:
>>
>> I’m working on a filesystem for OS X on which modifications may
>> occur without going through the VFS (kind of like NFS).
>>
>> Looking at the source of XNU, I can see that NFS uses the FSEvents
>> kernel-side API to push filesystem events. I’d like to do the same
>> with my filesystem.
>
> I presume you are referring to the NFS server's use of add_fsevent().
> Note that this is in the NFS *server* and not the NFS client file system.
> The NFS server code built into xnu can generate local fsevents for
> operations it performs on behalf of its clients - that's done primarily
> because the NFS server calls into the exported file systems below the VFS
> layer that fsevents are normally generated in.
>
>> The problem is: I can’t find the header file for fsevents in the
>> Mac OS X SDK. Do Kernel Extensions have access to the FSEvents API
>> (as providers)? Am I missing a Kernel SDK or something similar?
>
> The VFS fsevents interface is private and thus use by third parties is
> not supported.
>
> 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.
>
> --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