GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Checking which kernel limit is breached
Operating System - HP-UX
1846585
Members
2963
Online
110256
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
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
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
10-07-2002 02:09 PM
10-07-2002 02:09 PM
Checking which kernel limit is breached
How can I dynamically check global counts to determine which kernel tunable setting is being breached? I'm running a c program which does a tp-connect into a remote Tuxedo service, in order to simulate 25,000 Tuxedo connections. Each tp-connect runs in a Unix process, and we are able to start 16,348 before the next one fails. The failure is on the local system, where the only values in the region of 16348 are msgseg and semaem - both are 16384, but neither seems relevant to the problem.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-07-2002 02:19 PM
10-07-2002 02:19 PM
Re: Checking which kernel limit is breached
Hi Dave:
The system table report of 'glance' [toggled with a 't'] is useful for a few kernel parameters. 'sar -v' is valuable for several too.
You might find it useful to list the values and limits of your tuned set with:
# kmtune -l
Additionally, it is always useful to consult '/usr/include/sys/errno.h' for the meaning of 'errno'.
Regards!
...JRF...
The system table report of 'glance' [toggled with a 't'] is useful for a few kernel parameters. 'sar -v' is valuable for several too.
You might find it useful to list the values and limits of your tuned set with:
# kmtune -l
Additionally, it is always useful to consult '/usr/include/sys/errno.h' for the meaning of 'errno'.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-07-2002 07:52 PM
10-07-2002 07:52 PM
Re: Checking which kernel limit is breached
Hi,
#sar -v 1 10
This will monitor
6:53 text-sz ov proc-sz ov inod-sz ov file-sz ov
The related kernel paramters are
1) nproc
2) ninode
3) nfiles
regards,
U.SivaKumar
#sar -v 1 10
This will monitor
6:53 text-sz ov proc-sz ov inod-sz ov file-sz ov
The related kernel paramters are
1) nproc
2) ninode
3) nfiles
regards,
U.SivaKumar
Innovations are made when conventions are broken
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 2026 Hewlett Packard Enterprise Development LP