topic Re: Lost Shared Memory Segments in Operating System - HP-UX

Lost Shared Memory Segments

Alex Green — Tue, 15 Jan 2002 16:54:05 GMT

Hi All,

I just wanted to ask all here, if anyone had some good suggestions as how to go about recovering lost shared memory segments. i.e. segments that we allocated and then not returned by an application. Thanks, if more detail is need, I can supply it.

Re: Lost Shared Memory Segments

A. Clay Stephenson — Tue, 15 Jan 2002 17:11:20 GMT

Hi:

I'm not sure that I understand your question. Did you set these up as IPC_PRIVATE? You might use ftok to set up a key and then recovery becomes simple. If you will post just a bit of the code or outline the process better, I or someone else can probably help more.

Re: Lost Shared Memory Segments

Bill Hassell — Tue, 15 Jan 2002 20:08:08 GMT

Start with:

ipcs -bmop

Look for NATTCH = 0 and determine if that segment is no longer necessary. Then use ipcrm to remove that segment.

To get a better picture of shared memory, get a copy of shminfo from:

ftp://contrib:9unsupp8@hprc.external.hp.com/sysadmin/programs/shminfo

You'll also get a copy of a simple program to test shared memory allocation.

Re: Lost Shared Memory Segments

A. Clay Stephenson — Tue, 15 Jan 2002 20:18:06 GMT

Hi:

I will add that NATTACH = 0 is a necessary but not always sufficient condition to detach a shared memory segment. It may be that a process created the segment for a group of processes to utilize. Just because no processes have it attached at the moment does not mean that it is always safe to remove. A critical process could die or fail to start if it could not find the segment. I was reluctant to mention ipcrm until I knew a few more details. As usual with things UNIX, the answer is it depends.

I will certainly concede that most of the time the NATTACH = 0 condition indicates that it is okay to blow this guy away.

Regards, Clay