The shared memory files are created in /dev/shm/... on linux, but the code
tries to find them in your home account. Since the file doesn't exist, a 0
is returned from ftok. This results in a pileup of shm's and semaphores. Run
ipcs -a after every run to see the probmem.
Cal Page
Here's the
Hi,
Applied to to SVN HEAD/2.6/2.4 branches.
Zoltan
On Fri, Mar 5, 2010 at 6:21 PM, cpMon page@gmail.com wrote:
The shared memory files are created in /dev/shm/... on linux, but the code
tries to find them in your home account. Since the file doesn't exist, a 0
is
