• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: FSEvents API not working after restarting fseventsd daemon
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: FSEvents API not working after restarting fseventsd daemon

  • Subject: Re: FSEvents API not working after restarting fseventsd daemon
  • From: Ashish Saxena <email@hidden>
  • Date: Sat, 14 Jun 2014 20:25:05 +0530


> 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.

Instead of going the bug route, I am interested in finding a solution that would work with current library. So, asking it again - is there any cleanup method that can be called by the application to reset this state (resetting runloop states or reinitializing the carbon framework internal state or reloading the library - just thinking about different possible options as I am new to Mac development). 
 _______________________________________________
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
References: 
 >FSEvents API not working after restarting fseventsd daemon (From: Ashish Saxena <email@hidden>)
 >Re: FSEvents API not working after restarting fseventsd daemon (From: Mike Mackovitch <email@hidden>)
 >Re: FSEvents API not working after restarting fseventsd daemon (From: Ashish Saxena <email@hidden>)
 >Re: FSEvents API not working after restarting fseventsd daemon (From: Mike Mackovitch <email@hidden>)

  • Prev by Date: Re: FSEvents API not working after restarting fseventsd daemon
  • Next by Date: Re: Finder does not see any content behind a mount point
  • Previous by thread: Re: FSEvents API not working after restarting fseventsd daemon
  • Next by thread: Time Machine internals, anyone?
  • Index(es):
    • Date
    • Thread