<?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 dmesg  and /dev/kmem in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-and-dev-kmem/m-p/2539738#M26438</link>
    <description>We are running HP-UX 11.0 on 9000 class machines.&lt;BR /&gt;&lt;BR /&gt;What should the permissions be for dmesg and /dev/kmem ? dmesg only works for user root because /dev/kmem is not readable for everyone. Some casual users need to run dmesg to get the Physical memory info. &lt;BR /&gt;(We do not have dmesg dumping to /var/adm/messages.)&lt;BR /&gt;&lt;BR /&gt;Solaris has 3555 permissions on for dmesg and 640 for kmem. I checked a HP 9000 server in another admin group we have and they had /dev/kmem set at 644 and dmesg at 555 which allows dmesg to work for common users.&lt;BR /&gt;&lt;BR /&gt;Here is what I have:&lt;BR /&gt;crw-r-----   1 bin      sys     3 0x000001 Jan 19  2000 /dev/kmem&lt;BR /&gt;-r-xr-xr-x   1 bin        bin         155648 Nov  7  1997 /sbin/dmesg</description>
    <pubDate>Tue, 12 Jun 2001 18:03:20 GMT</pubDate>
    <dc:creator>motorola_austin</dc:creator>
    <dc:date>2001-06-12T18:03:20Z</dc:date>
    <item>
      <title>dmesg  and /dev/kmem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-and-dev-kmem/m-p/2539738#M26438</link>
      <description>We are running HP-UX 11.0 on 9000 class machines.&lt;BR /&gt;&lt;BR /&gt;What should the permissions be for dmesg and /dev/kmem ? dmesg only works for user root because /dev/kmem is not readable for everyone. Some casual users need to run dmesg to get the Physical memory info. &lt;BR /&gt;(We do not have dmesg dumping to /var/adm/messages.)&lt;BR /&gt;&lt;BR /&gt;Solaris has 3555 permissions on for dmesg and 640 for kmem. I checked a HP 9000 server in another admin group we have and they had /dev/kmem set at 644 and dmesg at 555 which allows dmesg to work for common users.&lt;BR /&gt;&lt;BR /&gt;Here is what I have:&lt;BR /&gt;crw-r-----   1 bin      sys     3 0x000001 Jan 19  2000 /dev/kmem&lt;BR /&gt;-r-xr-xr-x   1 bin        bin         155648 Nov  7  1997 /sbin/dmesg</description>
      <pubDate>Tue, 12 Jun 2001 18:03:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-and-dev-kmem/m-p/2539738#M26438</guid>
      <dc:creator>motorola_austin</dc:creator>
      <dc:date>2001-06-12T18:03:20Z</dc:date>
    </item>
    <item>
      <title>Re: dmesg  and /dev/kmem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-and-dev-kmem/m-p/2539739#M26439</link>
      <description>I would set /dev/mem and /dev/kmem to 644 but make sure that it is owned by root. 555 for dmesg and again owned by root.&lt;BR /&gt;&lt;BR /&gt;Clay&lt;BR /&gt;</description>
      <pubDate>Tue, 12 Jun 2001 18:11:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-and-dev-kmem/m-p/2539739#M26439</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2001-06-12T18:11:39Z</dc:date>
    </item>
    <item>
      <title>Re: dmesg  and /dev/kmem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-and-dev-kmem/m-p/2539740#M26440</link>
      <description>Hi again,&lt;BR /&gt;&lt;BR /&gt;Be awrare that dmesg will not always display memory; dmesh uses a circular buffer and once that is overwritten; the initial data is gone.&lt;BR /&gt;</description>
      <pubDate>Tue, 12 Jun 2001 18:12:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-and-dev-kmem/m-p/2539740#M26440</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2001-06-12T18:12:52Z</dc:date>
    </item>
  </channel>
</rss>

