<?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 Re: processor count using adb in vPar environment in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/processor-count-using-adb-in-vpar-environment/m-p/3741824#M786322</link>
    <description>vparstatus|awk 'NF==9 {print $0}'|awk '{print $1,$4,$5}'|while read vpar&lt;BR /&gt; c1 c2;do&lt;BR /&gt;           printf "     %12s   %4d cpus\n" $vpar $((c1+c2))&lt;BR /&gt;done&lt;BR /&gt;</description>
    <pubDate>Wed, 01 Mar 2006 13:32:38 GMT</pubDate>
    <dc:creator>Alzhy</dc:creator>
    <dc:date>2006-03-01T13:32:38Z</dc:date>
    <item>
      <title>processor count using adb in vPar environment</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/processor-count-using-adb-in-vpar-environment/m-p/3741819#M786317</link>
      <description>For the longest time I have been using the below to retrieve the number of processors on a system for reporting.&lt;BR /&gt;echo "runningprocs/D"|adb -k /stand/vmunix /dev/mem&lt;BR /&gt;&lt;BR /&gt;In a vPar environment with ICOD this reports all procs minus the two bound to the other vPar.&lt;BR /&gt;&lt;BR /&gt;Is there another kernel var that can be used to report the current number of processors active in a vPar I only see runningprocs in /usr/include/sys/ki_calls.h ??&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 01 Mar 2006 10:27:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/processor-count-using-adb-in-vpar-environment/m-p/3741819#M786317</guid>
      <dc:creator>Tim Nelson</dc:creator>
      <dc:date>2006-03-01T10:27:27Z</dc:date>
    </item>
    <item>
      <title>Re: processor count using adb in vPar environment</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/processor-count-using-adb-in-vpar-environment/m-p/3741820#M786318</link>
      <description>Tim,&lt;BR /&gt;&lt;BR /&gt;How about the vparstatus command?&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Robert-Jan</description>
      <pubDate>Wed, 01 Mar 2006 10:50:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/processor-count-using-adb-in-vpar-environment/m-p/3741820#M786318</guid>
      <dc:creator>Robert-Jan Goossens</dc:creator>
      <dc:date>2006-03-01T10:50:45Z</dc:date>
    </item>
    <item>
      <title>Re: processor count using adb in vPar environment</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/processor-count-using-adb-in-vpar-environment/m-p/3741821#M786319</link>
      <description>That is where I was headed next if no answer to using adb.&lt;BR /&gt;&lt;BR /&gt;Note:&lt;BR /&gt;Also noticed adb hangs on one partition and not the other.&lt;BR /&gt;&lt;BR /&gt;Using adb64 works for some items but not others.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 01 Mar 2006 10:53:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/processor-count-using-adb-in-vpar-environment/m-p/3741821#M786319</guid>
      <dc:creator>Tim Nelson</dc:creator>
      <dc:date>2006-03-01T10:53:07Z</dc:date>
    </item>
    <item>
      <title>Re: processor count using adb in vPar environment</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/processor-count-using-adb-in-vpar-environment/m-p/3741822#M786320</link>
      <description>I don't think so -- and I wouldn't recommend it anyway. Reading kernel internal variables is a good way to have stuff break on you between patches/releases in the first place.&lt;BR /&gt;&lt;BR /&gt;You can get this information from pstat, attaching a C program to do so.</description>
      <pubDate>Wed, 01 Mar 2006 10:53:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/processor-count-using-adb-in-vpar-environment/m-p/3741822#M786320</guid>
      <dc:creator>Don Morris_1</dc:creator>
      <dc:date>2006-03-01T10:53:10Z</dc:date>
    </item>
    <item>
      <title>Re: processor count using adb in vPar environment</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/processor-count-using-adb-in-vpar-environment/m-p/3741823#M786321</link>
      <description>Here is some more info relating to adb failing/hanging  in a vpar environment.  KnowledgeBase DOC. 4000067733&lt;BR /&gt;&lt;BR /&gt;adb fails/hangs in vPar as it has trouble accessing the higher memory region that the vPar &amp;gt; 1 runs in.  Aquire the new ADB or use /dev/kmem instead of /dev/mem&lt;BR /&gt;</description>
      <pubDate>Wed, 01 Mar 2006 11:13:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/processor-count-using-adb-in-vpar-environment/m-p/3741823#M786321</guid>
      <dc:creator>Tim Nelson</dc:creator>
      <dc:date>2006-03-01T11:13:32Z</dc:date>
    </item>
    <item>
      <title>Re: processor count using adb in vPar environment</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/processor-count-using-adb-in-vpar-environment/m-p/3741824#M786322</link>
      <description>vparstatus|awk 'NF==9 {print $0}'|awk '{print $1,$4,$5}'|while read vpar&lt;BR /&gt; c1 c2;do&lt;BR /&gt;           printf "     %12s   %4d cpus\n" $vpar $((c1+c2))&lt;BR /&gt;done&lt;BR /&gt;</description>
      <pubDate>Wed, 01 Mar 2006 13:32:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/processor-count-using-adb-in-vpar-environment/m-p/3741824#M786322</guid>
      <dc:creator>Alzhy</dc:creator>
      <dc:date>2006-03-01T13:32:38Z</dc:date>
    </item>
  </channel>
</rss>

