site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Thanks, -- Terry On May 14, 2008, at 8:35 AM, Jim Correia <jim.correia@pobox.com> wrote: Which is the correct case? Jim _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/tlambert%40apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... It's not that clear to me that what you are presuming is the source of the NOTE_ATTRIB wakeups is in fact the actual source of them. Your assumption that this is due to atime updates may not be correct. Even if it is correct, however, there is room for interpretation from both the POSIX side of things (i.e. should events trigger as a result of "shall be marked for update" v.s. "shall be updated") and the philosophical side of things (i.e. is resource fork information data or metadata, and are events on it events on the fork or events on the file to which the fork is attached?). It would probably be best if you filed a bug, including with it sample code to demonstrate it properly (likely two programs, one to observe, one to trigger), along with an explanation as to why you think it's a bug. I have a file that I am observing with kevents. I am observing with the NOTE_ATTRIB flag set. (For this test case, I am using an HFS+ disk on Leopard.) Most things which bump the access time of the file do not cause my kevent observer to fire. (For example, `cat filename` bumps the access time, doesn't fire the kevent.) Some things, however, do. Any operation which causes the custom icon to be read from the resource fork (by opening the file in any Mac OS X GUI application.) bumps the access date and fires a kevent. I'm interested in many of the changes that come along with NOTE_ATTRIB, but I don't really care about the access date. Any advice for ignoring events for which only the access date change? This email sent to tlambert@apple.com This email sent to site_archiver@lists.apple.com