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 13:15:11 -0700
Hi Ashish,
On Sat, Jun 14, 2014 at 01:11:35AM +0530, Ashish Saxena wrote:
>
> I have a long running process that periodically (once every half hour) uses
> FSEvents API to find list of modified files in a particular folder. I am
> seeing following problem with the APIs:
Any particular reason you're not just leaving an FSEventStream open while
your long-running process runs? It takes more work to dig through historical
events because they need to be read out of on-disk logs.
> If fseventsd daemon is stopped and started (using launchctl or killing the
> process), then further calls to FSEvents API fails. FSEventsStreamStart()
> always fails after fseventsd is restarted. APIs like
> FSEventsGetCurrentEventId() starts returning 0 and
> FSEventsCopyUUIDForDevice() returns NULL UUID, both of which are wrong.
>
> Please let me know what is required to successfully call FSEvents API after
> restart of fseventd daemon. I want to take care of this issue so that my
> application starts using FSEvents even when fseventsd is restarted.
You should never need or want to stop/restart fseventsd.
fseventsd should always be running... otherwise events will be dropped.
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.
THanks
--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