Re: FSEvents API not working after restarting fseventsd daemon
Re: FSEvents API not working after restarting fseventsd daemon
- Subject: Re: FSEvents API not working after restarting fseventsd daemon
- From: Mike Mackovitch <email@hidden>
- Date: Fri, 13 Jun 2014 16:01:45 -0700
On Sat, Jun 14, 2014 at 02:41:32AM +0530, Ashish Saxena wrote:
>
> My app never stops/starts fseventsd. However, I want to make sure that the
> app does not miss any file change in any scenario - be it someone killing
> fseventsd or restarting it using the supported launchctl command. If the
> daemon is restarted, I detect that using changed UUID (and use alternative
> methods to detect changes).
While the launchctl command CAN be used to control launch daemons and agents,
using launchctl to turn off fseventsd is NOT supported by FSEvents.
> > If fseventsd isn't working properly, please file a bug with Apple.
> > If the FSEvents API isn't working properly, please file a bug with Apple.
> >
> > If the FSEvents API isn't working properly BECAUSE fseventsd is being
> > manipulated in unusual/unsupported ways, you can file a bug with Apple
> > but it probably won't be assigned a very high priority.
> Until fseventsd is stopped, everything works fine and the program print
> correct event ID values. However, when stopped, the program starts printing
> 0, and it keeps printing 0 forever - even long after the daemon comes up.
> My query is - is there some initialization/cleanup API that can be called
> to make the next call work correctly. If not, then I will open a bug with
> Apple.
Feel free to file a bug. But note that your use case is extremely unusual.
--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