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

[Alberto Villa]

On Thursday 09 September 2010 20:44:48 David Naylor wrote:
> Correct me if I'm wrong but doesn't python use shared memory with 
its
> multiprocess module (if built with semaphore support)?  It is only
> available in -current as far as I know.

...with p1003 1.b semaphores... it looks like they were made exactly 
with that destination in mind:

"POSIX 1003.1b semaphores provide an efficient form of interprocess 
communication. Cooperating processes can use semaphores to 
synchronize access to resources, most commonly, shared memory."

can anyone explain the differences between them and pthread 
process shared sync? otherwise i'll study the whole issue in - as said - 
a couple of weeks from now, and eventually make a patch for kde

meanwhile, i'm writing to KSharedDataCache author
-- 
Alberto Villa, FreeBSD Committer <avilla at FreeBSD.org>
http://people.FreeBSD.org/~avilla

The only person who always got his work done by Friday was Robinson 
Crusoe.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 314 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-freebsd/attachments/20100909/a3a7a648/attachment.sig