Re: Locking a shared memory object (crash safe )
site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com User-agent: Thunderbird 2.0.0.12 (Windows/20080213) Thanks Nick _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... Jonas Maebe wrote: Note that if you unlink the semaphore right after creating it, trying to sem_open() the same semaphore (i.e., passing the same name to sem_open) will get you a new semaphore rather than the previously opened/unlinked one (and this may or may not be a problem). As far as I understand it, other processes (started later) would then create their own (independent) semaphore which would defy the purpose of what I am trying to achieve (allowing a cross process lock). This email sent to site_archiver@lists.apple.com
participants (1)
-
Nicholaz Beresford