On Sat, Feb 19, 2011 at 1:20 PM, Alexander Cohen <[email protected]> wrote: > Yeah, that seems like a good option but since its based off of flock, it has > the same issues. Things like apps crashing or not unlocking by error will > prevent other processes from obtaining the lock even though the lock is not > 'really' in use anymore.
If an app crashes or exits then the OS automatically releases all its resources, including flocks. I don't know why you would think otherwise. If your app has an error where some code path fails to unlock... well, that's an issue across almost every locking primitive. Personally, I'd use semget in this case. But nothing wrong with flock. _______________________________________________ Cocoa-dev mailing list ([email protected]) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
