<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Checking which kernel limit is breached in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/checking-which-kernel-limit-is-breached/m-p/2820427#M86459</link>
    <description>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.</description>
    <pubDate>Mon, 07 Oct 2002 21:09:27 GMT</pubDate>
    <dc:creator>Dave Hewetson</dc:creator>
    <dc:date>2002-10-07T21:09:27Z</dc:date>
    <item>
      <title>Checking which kernel limit is breached</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/checking-which-kernel-limit-is-breached/m-p/2820427#M86459</link>
      <description>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.</description>
      <pubDate>Mon, 07 Oct 2002 21:09:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/checking-which-kernel-limit-is-breached/m-p/2820427#M86459</guid>
      <dc:creator>Dave Hewetson</dc:creator>
      <dc:date>2002-10-07T21:09:27Z</dc:date>
    </item>
    <item>
      <title>Re: Checking which kernel limit is breached</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/checking-which-kernel-limit-is-breached/m-p/2820428#M86460</link>
      <description>Hi Dave:&lt;BR /&gt;&lt;BR /&gt;The system table report of 'glance' [toggled with a 't'] is useful for a few kernel parameters.  'sar -v' is valuable for several too.&lt;BR /&gt;&lt;BR /&gt;You might find it useful to list the values and limits of your tuned set with:&lt;BR /&gt;&lt;BR /&gt;# kmtune -l&lt;BR /&gt;&lt;BR /&gt;Additionally, it is always useful to consult '/usr/include/sys/errno.h' for the meaning of 'errno'.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Mon, 07 Oct 2002 21:19:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/checking-which-kernel-limit-is-breached/m-p/2820428#M86460</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2002-10-07T21:19:06Z</dc:date>
    </item>
    <item>
      <title>Re: Checking which kernel limit is breached</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/checking-which-kernel-limit-is-breached/m-p/2820429#M86461</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;#sar -v 1 10&lt;BR /&gt;&lt;BR /&gt;This will monitor &lt;BR /&gt;6:53 text-sz  ov  proc-sz  ov  inod-sz  ov  file-sz  ov &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;The related kernel paramters are&lt;BR /&gt;1) nproc&lt;BR /&gt;2) ninode&lt;BR /&gt;3) nfiles&lt;BR /&gt;&lt;BR /&gt;regards,&lt;BR /&gt;U.SivaKumar        &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 08 Oct 2002 02:52:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/checking-which-kernel-limit-is-breached/m-p/2820429#M86461</guid>
      <dc:creator>U.SivaKumar_2</dc:creator>
      <dc:date>2002-10-08T02:52:40Z</dc:date>
    </item>
  </channel>
</rss>

