• 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: Aaron Burghardt <email@hidden>
  • Date: Sun, 02 Dec 2012 17:08:36 -0500


On Dec 2, 2012, at 7:26 AM, Arun prabu <email@hidden> wrote:

Another question. Whenever a file is modified, the events are sent only after the file is closed. Is there a way to get events everytime the file is flushed instead of when the file is closed. Because, there are some applications which frequently writes data to a file. The data is flushed at regular intevals but the file is closed when the application exits. In such case, content modified event will be received at the end eventhough data is already flushed to the disk at multiple intervals.
 
The behaviour is same in /dev/fsevents and also FSEvents API.

Are you watching a select number of files? In that case, kevents might work for you ('man kevent'). The EVFILT_VNODE filter can report a number of events, including writes. Unlike FSEvents, you have to register each path you wish to watch.

Aaron

 _______________________________________________
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

  • Follow-Ups:
    • Re: FSE_ARG_INT64 argument in fsevent
      • From: Arun prabu <email@hidden>
References: 
 >Re: FSE_ARG_INT64 argument in fsevent (From: Arun prabu <email@hidden>)

  • Prev by Date: Re: FSE_ARG_INT64 argument in fsevent
  • Next by Date: Re: FSE_ARG_INT64 argument in fsevent
  • Previous by thread: Re: FSE_ARG_INT64 argument in fsevent
  • Next by thread: Re: FSE_ARG_INT64 argument in fsevent
  • Index(es):
    • Date
    • Thread