- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- HPUX 10.20 kernel parms: MSGSSZ & SEMMNU
Categories
Company
Local Language
Forums
Discussions
- Integrity Servers
- Server Clustering
- HPE NonStop Compute
- HPE Apollo Systems
- High Performance Computing
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Knowledge Base
Forums
Discussions
- Cloud Mentoring and Education
- Software - General
- HPE OneView
- HPE Ezmeral Software platform
- HPE OpsRamp Software
Knowledge Base
Discussions
Forums
Discussions
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
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
02-04-2002 03:11 PM
02-04-2002 03:11 PM
Lawson support center recommended we increase our MSGSSZ & SEMMNU kernel parameter values from "8" to "128" and from "515" to "1024" respectively. We just did that this afternoon.
My question is ... how can we proactively measure the application use of those kernel parameters to determine if the new values are adequate?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-04-2002 04:22 PM
02-04-2002 04:22 PM
Re: HPUX 10.20 kernel parms: MSGSSZ & SEMMNU
Do a 'man' on ipcs and see if this fits the bill.
HTH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-04-2002 04:39 PM
02-04-2002 04:39 PM
Re: HPUX 10.20 kernel parms: MSGSSZ & SEMMNU
# ipcs -bcopt | more
IPC status from /dev/kmem as of Mon Feb 4 16:38:37 2002
T ID KEY MODE OWNER GROUP CREATOR CGROUP CBYTES QNUM QBYTES LSPID LRPID STIME RTIME CTIME
Message Queues:
q 485 0x70700000 -Rrw-rw-rw- root lawson root lawson 0 0 7200 5337 2821 16:38:34 16:38:34 14:31:35
q 486 0x70700001 --rw-rw-rw- root lawson root lawson 0 0 72 0 0 no-entry no-entry 14:31:35
q 487 0x70700002 --rw-rw-rw- root lawson root lawson 0 0 36 2842 2841 16:37:01 16:37:01 14:31:35
q 488 0x70700003 --rw-rw-rw- root lawson root lawson 0 0 36 2831 2830 16:38:15 16:38:15 14:31:35
Should I be looking at the CBYTES & QBYTES columns? When do I know I am about to "run out" of the message queue resources for the present kernel parameter value?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-04-2002 04:56 PM
02-04-2002 04:56 PM
SolutionTBL_PROC_TABLE_AVAIL
TBL_PROC_TABLE_USED
So I created a file called "test" and had this statement in it ..
print TBL_PROC_TABLE_AVAIL, TBL_PROC_TABLE_USED
then I ran glance as such ..
# glance -iterations 1 -adviser_only -syntax test
and I would get 2 column (available and used), you can probably expand on this for your use.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-05-2002 01:35 PM
02-05-2002 01:35 PM
Re: HPUX 10.20 kernel parms: MSGSSZ & SEMMNU
System Table Available Used Utilization High(%)
--------------------------------------------------------------------------------
Proc Table (nproc) 2420 345 14 14
File Table (nfile) 4659 1525 33 33
Shared Mem Table (shmmni) 200 16 8 8
Message Table (msgmni) 485 376 78 78
Semaphore Table (semmni) 128 23 18 18
File Locks (nflocks) 200 57 29 29
Psuedo Terminals (npty) 60 8 13 13
Buffer Headers (nbuf) na 202308 na na
Is there a way to get glance-plus to show all configured tunable parameters and their status? Or are the ones available the only ones that make sense in this format?