FSEvents API not working after restarting fseventsd daemon
FSEvents API not working after restarting fseventsd daemon
- Subject: FSEvents API not working after restarting fseventsd daemon
- From: Ashish Saxena <email@hidden>
- Date: Sat, 14 Jun 2014 01:11:35 +0530
Hi,
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:
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.
Thanks,
Ashish
_______________________________________________
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