- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: semaphore key 0x00000000
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
08-08-2003 02:31 PM
08-08-2003 02:31 PM
semaphore key 0x00000000
my question is - can I just remove these ipcrm -s since they have key 0x00000000 ?
Lisa
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-08-2003 04:25 PM
08-08-2003 04:25 PM
Re: semaphore key 0x00000000
Try removing with the ID rather than the key
ipcrm -s (ID) right in front of the key. also look into shminfo.
Thanks
Giri Sekar.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-08-2003 05:04 PM
08-08-2003 05:04 PM
Re: semaphore key 0x00000000
my question was more along the lines of ...
can I assume that it is safe to remove these entries with the key of 0x00000000 ?
is there a case where an entry with a key of 0x00000000 is still valid and removing it could cause a problem for an active process - or is my recollection that these 0x00000000 entries are essentially orphans and it is safe to remove them without regard for where they came from?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-08-2003 05:53 PM
08-08-2003 05:53 PM
Re: semaphore key 0x00000000
I certainly think its a valid key, although I don't know if it is encouraged when multiple processes could access the semaphore. When a semaphore is created using the IPC_PRIVATE flag of semget, only that process and its children can access the semaphore. Multiple instances of any key can be created in this fashion but they will have different ids. I would use "ipcs -sa" to check the number of semaphore sets (nsems) corresponding to it and the last access times etc, see "man ipcs" for a description of the fields.
regards,
James.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-08-2003 07:45 PM
08-08-2003 07:45 PM
Re: semaphore key 0x00000000
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-08-2003 10:33 PM
08-08-2003 10:33 PM
Re: semaphore key 0x00000000
There is an HP contributed tool named seminfo which will show you this, contact your local RC for this. Without this its a lot harder, you need to use a kernel debugger.
first, find your semmni value:
# kmtune|grep semmni
Next, use ipcs -s to find the key you want to use, in your case 0x00000000 I believe. This is the hard bit:
# ied q4 /stand/vmunix /dev/kmem
q4> load struct semid_ds from &sema max
q4> keep sem_perm.key ==
q4> load struct __sem from sem_base
q4> print sempid
sempid
2071
So here I see process 2071 was using this semaphore. If you have multiple keys using the same value you will see multiple structs being loaded. You can use "print -tx" in q4 to try and find a unique value a particular structure to keep using the same syntax as the above keep command.
Regards,
James.