Re: Notification of file system modification arrives too early?
Re: Notification of file system modification arrives too early?
- Subject: Re: Notification of file system modification arrives too early?
- From: Jens Alfke <email@hidden>
- Date: Sun, 30 May 2010 09:51:44 -0700
On May 30, 2010, at 7:57 AM, James Bucanek wrote:
> When a change occurs, I attempt to open the file using the FS API specifying exclusive read + exclusive write access. If it fails, it's likely because some other process still has the file open. I delay a half second or so and try again.
That sounds like a good approach, but it’s not 100% reliable. If the creating process opened the file without requesting an exclusive lock, then your open call will succeed even though the file is still open.
Unfortunately you probably can’t do any better than that, since there’s no cheap way to find out if another process has the file open.
—Jens_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden