[kde-freebsd] Failed to establish shared memory mapping, will fallback to private memory

[Andriy Gapon]

on 10/09/2010 10:41 Alberto Villa said the following:
> On Friday 10 September 2010 07:38:42 Andriy Gapon wrote:
>> If that's what is needed (e.g. process-shared mutexes), then we are 
> out of
>> luck. Adding this feature would require some significant changes in
>> supposedly opaque part of pthreads API implementation.  And so it is
>> unlikely to happen in near future.  This has been discussed couple of
>> times on freebsd-threads at .
> 
> and what dou you know about the semaphores i mentioned?

POSIX semaphores are known to work well.
See sem(4), sem_open(3).
I think that (unnamed) POSIX semaphores in shared memory are successfully used by
Firefox and Python.

-- 
Andriy Gapon