<?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: dmesg command in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-command/m-p/2528234#M24680</link>
    <description>Try with STM command:&lt;BR /&gt;#echo "selclass qualifier memory;info;wait;infolog"|cstm</description>
    <pubDate>Tue, 15 May 2001 11:36:50 GMT</pubDate>
    <dc:creator>Vincenzo Restuccia</dc:creator>
    <dc:date>2001-05-15T11:36:50Z</dc:date>
    <item>
      <title>dmesg command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-command/m-p/2528232#M24678</link>
      <description>Hello,&lt;BR /&gt;I would like to use the physical memory output from the dmesg command in a script that monitors the free system memory.  However, my dmesg is 'full' and I am trying to find a way to 'clear' it and get the memory report again.  I have tried /usr/sam/lbin/getmem and it gives false output (report 512MB on systems with 2GB).  I don't want to use syslog.log or OLDsyslog.log, for fear of the syslogd getting restarted, or the log files getting deleted by some well-meaning admin and the memory info getting lost.  Running 10.20 on 9000's - is there a way to refresh dmesg?&lt;BR /&gt;Thanks&lt;BR /&gt;Eric Liszka</description>
      <pubDate>Mon, 14 May 2001 20:43:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-command/m-p/2528232#M24678</guid>
      <dc:creator>EDMS SST</dc:creator>
      <dc:date>2001-05-14T20:43:23Z</dc:date>
    </item>
    <item>
      <title>Re: dmesg command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-command/m-p/2528233#M24679</link>
      <description>Hi Eric,&lt;BR /&gt;The dmesg buffer is circular and once it overflows the data is gone. A better way is to ask the kernel itself via adb.&lt;BR /&gt;Do this:&lt;BR /&gt;1) adb -k /stand/vmunix /dev/mem&lt;BR /&gt;2) physmem/D  (this will print the physical memory&lt;BR /&gt;in 4k pages)&lt;BR /&gt;3) $q (this will exit adb)&lt;BR /&gt;&lt;BR /&gt;Man adb for details. You could script the process and get the value anytime 'on the fly'.&lt;BR /&gt;&lt;BR /&gt;Hope this helps, Clay&lt;BR /&gt;</description>
      <pubDate>Mon, 14 May 2001 21:05:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-command/m-p/2528233#M24679</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2001-05-14T21:05:01Z</dc:date>
    </item>
    <item>
      <title>Re: dmesg command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-command/m-p/2528234#M24680</link>
      <description>Try with STM command:&lt;BR /&gt;#echo "selclass qualifier memory;info;wait;infolog"|cstm</description>
      <pubDate>Tue, 15 May 2001 11:36:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-command/m-p/2528234#M24680</guid>
      <dc:creator>Vincenzo Restuccia</dc:creator>
      <dc:date>2001-05-15T11:36:50Z</dc:date>
    </item>
    <item>
      <title>Re: dmesg command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-command/m-p/2528235#M24681</link>
      <description>Clay,&lt;BR /&gt;Thank you, that will do nicely......on all my systems except two.&lt;BR /&gt;On two systems the command just returns me to the shell with&lt;BR /&gt;no errors or output of any kind.  I've got the same binary, and same&lt;BR /&gt;permissions on /stand/vmunix and /dev/mem.  Any ideas on that one?&lt;BR /&gt;Thanks&lt;BR /&gt;Eric.</description>
      <pubDate>Tue, 15 May 2001 13:55:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-command/m-p/2528235#M24681</guid>
      <dc:creator>EDMS SST</dc:creator>
      <dc:date>2001-05-15T13:55:58Z</dc:date>
    </item>
    <item>
      <title>Re: dmesg command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-command/m-p/2528236#M24682</link>
      <description>Hi Erik:&lt;BR /&gt;&lt;BR /&gt;On 10.x systems:&lt;BR /&gt;&lt;BR /&gt;# echo "physmem/D"|adb -k /stand/vmunix /dev/kmem&lt;BR /&gt;&lt;BR /&gt;On 11.x 32-bit systems:&lt;BR /&gt;&lt;BR /&gt;# echo "phys_mem_pages/D"|adb /stand/vmunix /dev/kmem&lt;BR /&gt;&lt;BR /&gt;On 11.x 64-bit systems:&lt;BR /&gt;&lt;BR /&gt;echo "phys_mem_pages/D"|adb64 -k /stand/vmunix /dev/mem&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Tue, 15 May 2001 14:04:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-command/m-p/2528236#M24682</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2001-05-15T14:04:18Z</dc:date>
    </item>
    <item>
      <title>Re: dmesg command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-command/m-p/2528237#M24683</link>
      <description>difference between 10.20 and 11.00?  :)&lt;BR /&gt;&lt;BR /&gt;try "phys_mem_pages/D" for 11.x&lt;BR /&gt;good luck,&lt;BR /&gt;Thierry.</description>
      <pubDate>Tue, 15 May 2001 14:05:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-command/m-p/2528237#M24683</guid>
      <dc:creator>Thierry Poels_1</dc:creator>
      <dc:date>2001-05-15T14:05:10Z</dc:date>
    </item>
    <item>
      <title>Re: dmesg command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-command/m-p/2528238#M24684</link>
      <description>Hi Eric,&lt;BR /&gt;I think James answered your question. I suspect you have some 11x boxes mixed in rather than simply the 10.20 OS you mentioned.&lt;BR /&gt;If the suggestions made by James don't fix your problem then let us know what OS and machine type. There were a few patches for adb and you may need to install one.&lt;BR /&gt;&lt;BR /&gt;Regards, Clay&lt;BR /&gt;</description>
      <pubDate>Tue, 15 May 2001 14:16:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-command/m-p/2528238#M24684</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2001-05-15T14:16:47Z</dc:date>
    </item>
    <item>
      <title>Re: dmesg command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-command/m-p/2528239#M24685</link>
      <description>Thank you,&lt;BR /&gt;These two are running 10.20, I was able to get into adb without the -k option but physmem and phys_mem_pages were bad values.  According to uname -a:&lt;BR /&gt;HP-UX B.10.20 A 9000/898&lt;BR /&gt;on both systems.&lt;BR /&gt;&lt;BR /&gt;Eric.</description>
      <pubDate>Tue, 15 May 2001 14:24:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-command/m-p/2528239#M24685</guid>
      <dc:creator>EDMS SST</dc:creator>
      <dc:date>2001-05-15T14:24:50Z</dc:date>
    </item>
    <item>
      <title>Re: dmesg command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-command/m-p/2528240#M24686</link>
      <description>It's a very good idea to capture all dmesg output.  SInce it can easily fill up with other console messges, it must be captured via cron.  The sample cron entry in /usr/newconfig (all sysadmins should remember this directory) has an example:&lt;BR /&gt;&lt;BR /&gt;# log kernel diagnostic messages every 10 minutes&lt;BR /&gt;05,15,25,35,45,55 * * * * /usr/sbin/dmesg - &amp;gt;&amp;gt;/var/adm/dmesg.log&lt;BR /&gt;&lt;BR /&gt;Note that the demsg - option is important as it asks only for changes since the last call to demsg.  I use the logname: dmesg.log while the example in /usr/newconfig/var/spool/cron/crontab.root is /var/adm/messages.&lt;BR /&gt;&lt;BR /&gt;Now there won't be any lost messages.&lt;BR /&gt;&lt;BR /&gt;A note about cstm...a very important tool but not installed automatically.  Install cstm (and it's siblings mstm and xstm) from the SupportPlus CDROM in the DIAGNOSTICS directory.</description>
      <pubDate>Wed, 16 May 2001 00:45:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-command/m-p/2528240#M24686</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2001-05-16T00:45:42Z</dc:date>
    </item>
    <item>
      <title>Re: dmesg command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-command/m-p/2528241#M24687</link>
      <description>Hi Eric,&lt;BR /&gt;&lt;BR /&gt;Sorry I didn't see your last posting until now.&lt;BR /&gt;On the two errant boxes I would try this command.&lt;BR /&gt;&lt;BR /&gt;echo "physmem/D" | adb /stand/vmunix /dev/kmem&lt;BR /&gt;&lt;BR /&gt;You noted that the -k option was killin you so we will try it without the virtual to physical address mapping. Note that we are using a different mem device. I've never seen a case where adb would not run with -k.&lt;BR /&gt;&lt;BR /&gt;Clay&lt;BR /&gt;</description>
      <pubDate>Wed, 16 May 2001 01:20:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-command/m-p/2528241#M24687</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2001-05-16T01:20:18Z</dc:date>
    </item>
    <item>
      <title>Re: dmesg command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-command/m-p/2528242#M24688</link>
      <description>Clay,&lt;BR /&gt;Thanks again! using /dev/kmem without the -k option did the trick.&lt;BR /&gt;Eric.</description>
      <pubDate>Wed, 16 May 2001 13:41:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-command/m-p/2528242#M24688</guid>
      <dc:creator>EDMS SST</dc:creator>
      <dc:date>2001-05-16T13:41:00Z</dc:date>
    </item>
  </channel>
</rss>

