Is there some way, short of reinventing the wheel,
to use QLocks to protect memory aquired by segattach(2) after a fork?

I assume you mean that you segattach and then fork,
so that you have a segment shared between both
parent and child.

Probably the easiest thing to do in this case
would be to add a function that could register
a different region of memory to hold the QLp array
in qlock.c.

Russ

Reply via email to