Re: Locking a shared memory object (crash safe )
Re: Locking a shared memory object (crash safe )
- Subject: Re: Locking a shared memory object (crash safe )
- From: Nicholaz Beresford <email@hidden>
- Date: Wed, 19 Mar 2008 14:50:58 +0100
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).
Thanks
Nick
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden