On Mon, Jun 28, 2004 at 05:24:37PM -0700, Tyler 'Crackerjack' MacDonald wrote:
> I can understand the kernel not knowing that the memory is no longer used
> if there was still a straggler process hanging onto it. But when there are
> no processes left to access it, why does this continue to happen
Oyvind,
> That's expected. Since shared memory doesn't belong to a specific
> process, the kernel will not know when to clean up the memory.
When I was using libmm, I never had this problem. I could crash my software
a dozen times in an hour and still be able to get a fresh segment. I guess
tha
* Tyler 'Crackerjack' MacDonald <[EMAIL PROTECTED]>
|
| If I set up an apr_shmem segment on my Debian GNU/Linux system, and the
| master process that set up the segment crashes without closing it, the
| segment sticks around until I reboot.
That's expected. Since shared memory doesn't belong to
Package: libapr0
Version: 2.0.49
Severity: normal
If I set up an apr_shmem segment on my Debian GNU/Linux system, and the
master process that set up the segment crashes without closing it, the
segment sticks around until I reboot.
I'm using a file named "libbtt.shm" to back the segment on the fi
4 matches
Mail list logo
