HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- shared memory segment not released
Operating System - HP-UX
1834019
Members
2828
Online
110063
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-07-2007 08:39 PM
01-07-2007 08:39 PM
we have an rp8400 system running hpux11.11
some shared memory segment are not released when NATTCH value is equal to zero. is it a normal behaivor of the system ?
here is a portion of the output of ipcs command
T ID Key MODE OWNER GROUP
m 1013 0x412002e2 --rw-rw-rw- root sys
NATTCH ATIME DTIME CTIME
0 10:21:17 no-entry 0:06:12
this line describe a shared memory segment owned by root.
NATTCH=0 that means that there is no process attaching this segment: so this segment must be released.
ATIME=10:21:17 but DTIME=no-entry: that means that means that NATTCH should not be equal to zero.
could you help me to understand what is happening?
some shared memory segment are not released when NATTCH value is equal to zero. is it a normal behaivor of the system ?
here is a portion of the output of ipcs command
T ID Key MODE OWNER GROUP
m 1013 0x412002e2 --rw-rw-rw- root sys
NATTCH ATIME DTIME CTIME
0 10:21:17 no-entry 0:06:12
this line describe a shared memory segment owned by root.
NATTCH=0 that means that there is no process attaching this segment: so this segment must be released.
ATIME=10:21:17 but DTIME=no-entry: that means that means that NATTCH should not be equal to zero.
could you help me to understand what is happening?
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2007 09:13 PM
01-07-2007 09:13 PM
Re: shared memory segment not released
Shalom,
Sounds like bad programming, or a program that was supposed to be started by a non-priviledged user was started by root, which locked the memory segment.
If you cand identify and kill theprocess, the problem may go away.
You may need to use ipcrm to remove it.
ipcrm -m 1013
SEP
Sounds like bad programming, or a program that was supposed to be started by a non-priviledged user was started by root, which locked the memory segment.
If you cand identify and kill theprocess, the problem may go away.
You may need to use ipcrm to remove it.
ipcrm -m 1013
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2007 11:10 PM
01-07-2007 11:10 PM
Solution
Shared memory segments are never 'automatically' removed by the system. All management of these areas is by application programs. This is part of the design of shared resources. And the (very dangerous) kill -9 command will leave segments behind. Note that NATTCH can certainly be zero due to bad program design yet the segment(s) may be needed. You can manually remove unattached segments with the ipcrm if you're sure about current application usage.
Bill Hassell, sysadmin
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-08-2007 02:45 PM
01-08-2007 02:45 PM
Re: shared memory segment not released
The IPCRM command should be able to really get rid of the correct shared memory segement if you specify a IP.. IT can also be used for semiphore sets and message queues
good luck
Emil
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
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP