• 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: FSE_ARG_INT64 argument in fsevent
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: FSE_ARG_INT64 argument in fsevent


  • Subject: Re: FSE_ARG_INT64 argument in fsevent
  • From: Dominic Giampaolo <email@hidden>
  • Date: Fri, 30 Nov 2012 11:28:55 -0800

> I am using /dev/fsevents to receive file system events. For each event, there is an argument of type
>
Please do not do that.  There is no need to do that.
The FSEvents framework provides file-level events
now (and has since 10.7).


> FSE_ARG_INT64 which is 64 bits and the value keeps increasing for each event. It see different explation for this across internet. Some say this is not implemented and some say it represents timestamp. How should FSE_ARG_INT64 be interpreted.
>
Do not depend on the value in any way.  It is not any
form of a timestamp at all.  It is simply a counter
that increases.


--dominic


 _______________________________________________
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: 
 >FSE_ARG_INT64 argument in fsevent (From: Arun prabu <email@hidden>)

  • Prev by Date: Access to network volumes gets slower and slower within Finder and Time Machine. Issues and solutions
  • Previous by thread: FSE_ARG_INT64 argument in fsevent
  • Next by thread: Access to network volumes gets slower and slower within Finder and Time Machine. Issues and solutions
  • Index(es):
    • Date
    • Thread