<?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 in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg/m-p/3733144#M254845</link>
    <description>dmesg collects system diagnostic messages to form error log. The system error message buffer is of small, finite size.  dmesg is run only every few minutes, so there is no guarantee that all error messages will be logged. dmesg looks in a system buffer for recently printed diagnostic messages and prints them on the standard output.  The messages are those printed by the system when unusual events occur (such as when system tables overflow or the system crashes). &lt;BR /&gt;&lt;BR /&gt;In case of any issues with the system , first run #dmesg and check whether any errors are being logged: ex&lt;BR /&gt;a) SCSI lbolt errors&lt;BR /&gt;b) file system full&lt;BR /&gt;c) system tables overflow &lt;BR /&gt;&lt;BR /&gt;-Amit</description>
    <pubDate>Fri, 17 Feb 2006 04:55:49 GMT</pubDate>
    <dc:creator>Chauhan Amit</dc:creator>
    <dc:date>2006-02-17T04:55:49Z</dc:date>
    <item>
      <title>dmesg</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg/m-p/3733142#M254843</link>
      <description>Hi people, i saw the output of dmesg. So what exactly is it doing and how sould it determine me any problems on the system.</description>
      <pubDate>Thu, 16 Feb 2006 11:33:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dmesg/m-p/3733142#M254843</guid>
      <dc:creator>khilari</dc:creator>
      <dc:date>2006-02-16T11:33:55Z</dc:date>
    </item>
    <item>
      <title>Re: dmesg</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg/m-p/3733143#M254844</link>
      <description>You should start by reviewing the man page.  Dmesg collects system diagnostic messages in a circular buffer - that is, once it fills, it begins writing over itself and earlier messages are lost.  On a healthy system, all you will see from dmesg are start-up diagnostics from the last boot.  On a system that is having problems, you will see error messages logged that help identify the problem.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Pete</description>
      <pubDate>Thu, 16 Feb 2006 11:45:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dmesg/m-p/3733143#M254844</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2006-02-16T11:45:15Z</dc:date>
    </item>
    <item>
      <title>Re: dmesg</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg/m-p/3733144#M254845</link>
      <description>dmesg collects system diagnostic messages to form error log. The system error message buffer is of small, finite size.  dmesg is run only every few minutes, so there is no guarantee that all error messages will be logged. dmesg looks in a system buffer for recently printed diagnostic messages and prints them on the standard output.  The messages are those printed by the system when unusual events occur (such as when system tables overflow or the system crashes). &lt;BR /&gt;&lt;BR /&gt;In case of any issues with the system , first run #dmesg and check whether any errors are being logged: ex&lt;BR /&gt;a) SCSI lbolt errors&lt;BR /&gt;b) file system full&lt;BR /&gt;c) system tables overflow &lt;BR /&gt;&lt;BR /&gt;-Amit</description>
      <pubDate>Fri, 17 Feb 2006 04:55:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dmesg/m-p/3733144#M254845</guid>
      <dc:creator>Chauhan Amit</dc:creator>
      <dc:date>2006-02-17T04:55:49Z</dc:date>
    </item>
    <item>
      <title>Re: dmesg</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg/m-p/3733145#M254846</link>
      <description>Based on the error message and message type you can necessary steps into action.&lt;BR /&gt;&lt;BR /&gt;Please post messages or errors if you are not able to *fix* it.&lt;BR /&gt;&lt;BR /&gt;--&lt;BR /&gt;Muthu</description>
      <pubDate>Fri, 17 Feb 2006 04:59:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dmesg/m-p/3733145#M254846</guid>
      <dc:creator>Muthukumar_5</dc:creator>
      <dc:date>2006-02-17T04:59:04Z</dc:date>
    </item>
    <item>
      <title>Re: dmesg</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg/m-p/3733146#M254847</link>
      <description>&lt;BR /&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;dmesg looks in a system buffer for recently printed diagnostic messages and prints them on the standard output.  The messages are those printed by the system when unusual events occur (such as when system tables overflow or the system crashes).  If the - argument is specified, dmesg computes (incrementally) the new messages since the last time it was run and places these on the standard output.&lt;BR /&gt;&lt;BR /&gt;The man page has the right info.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Siva.</description>
      <pubDate>Fri, 17 Feb 2006 05:02:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dmesg/m-p/3733146#M254847</guid>
      <dc:creator>Sivakumar TS</dc:creator>
      <dc:date>2006-02-17T05:02:18Z</dc:date>
    </item>
    <item>
      <title>Re: dmesg</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg/m-p/3733147#M254848</link>
      <description>Hi Khilari, &lt;BR /&gt;&lt;BR /&gt;"dmesg" collect system diagnostic messages to form error log. &lt;BR /&gt;&lt;BR /&gt;Based on what kind of error you see on the log, you can debug from there.&lt;BR /&gt;&lt;BR /&gt;-Arun</description>
      <pubDate>Fri, 17 Feb 2006 05:02:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dmesg/m-p/3733147#M254848</guid>
      <dc:creator>Arunvijai_4</dc:creator>
      <dc:date>2006-02-17T05:02:44Z</dc:date>
    </item>
  </channel>
</rss>

