HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Lost Shared Memory Segments
Operating System - HP-UX
1825795
Members
2122
Online
109687
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-15-2002 08:54 AM
01-15-2002 08:54 AM
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.
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.
"The physicist's greatest tool is his wastebasket." - Albert Einstein.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-15-2002 09:11 AM
01-15-2002 09:11 AM
Re: Lost Shared Memory Segments
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.
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.
If it ain't broke, I can fix that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-15-2002 12:08 PM
01-15-2002 12:08 PM
Solution
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.
Bill Hassell, sysadmin
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.
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-15-2002 12:18 PM
01-15-2002 12:18 PM
Re: Lost Shared Memory Segments
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
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
If it ain't broke, I can fix that.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP