site_archiver@lists.apple.com Delivered-To: Darwin-dev@lists.apple.com What do you mean by "which task it is associated with at creation"? Is there any problem with this approach? Thanks Stephane _______________________________________________ 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... What is important for a Mach semaphore is which task it is associated with at creation. If it is associated with the client task and the client goes away, then operations on that semaphore by other tasks will fail (with an appropriate error code). So, choosing which task to associate with is important for widely shared semaphores. In my case the server main thread (the one that handle the client request : like new_client.....) will create the semaphore and pass them to clients. then client will wait on their semaphore, and another thread of the server *or* another thread of another client will signal the semaphore. This email sent to site_archiver@lists.apple.com