<?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: Examining Shared Memory in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/examining-shared-memory/m-p/4943724#M412183</link>
    <description>This link will probably work better since it includes the 9unsupp8 password.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;ftp://contrib:9unsupp8@hprc.external.hp.com/sysadmin/programs/shminfo/</description>
    <pubDate>Wed, 30 Nov 2005 16:44:43 GMT</pubDate>
    <dc:creator>A. Clay Stephenson</dc:creator>
    <dc:date>2005-11-30T16:44:43Z</dc:date>
    <item>
      <title>Examining Shared Memory</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/examining-shared-memory/m-p/4943722#M412181</link>
      <description>Is there a way, short of writing my own program, to examine the "contents" of a shared memory segment.  &lt;BR /&gt;&lt;BR /&gt;I can see the segment with ipcs, but need to examine the data values&lt;BR /&gt;&lt;BR /&gt;TIA&lt;BR /&gt;&lt;BR /&gt;Scott</description>
      <pubDate>Wed, 30 Nov 2005 16:24:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/examining-shared-memory/m-p/4943722#M412181</guid>
      <dc:creator>OldSchool</dc:creator>
      <dc:date>2005-11-30T16:24:10Z</dc:date>
    </item>
    <item>
      <title>Re: Examining Shared Memory</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/examining-shared-memory/m-p/4943723#M412182</link>
      <description>Get a copy of this utility:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="ftp://hprc.external.hp.com/sysadmin/programs/shminfo/" target="_blank"&gt;ftp://hprc.external.hp.com/sysadmin/programs/shminfo/&lt;/A&gt;</description>
      <pubDate>Wed, 30 Nov 2005 16:42:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/examining-shared-memory/m-p/4943723#M412182</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2005-11-30T16:42:55Z</dc:date>
    </item>
    <item>
      <title>Re: Examining Shared Memory</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/examining-shared-memory/m-p/4943724#M412183</link>
      <description>This link will probably work better since it includes the 9unsupp8 password.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;ftp://contrib:9unsupp8@hprc.external.hp.com/sysadmin/programs/shminfo/</description>
      <pubDate>Wed, 30 Nov 2005 16:44:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/examining-shared-memory/m-p/4943724#M412183</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2005-11-30T16:44:43Z</dc:date>
    </item>
    <item>
      <title>Re: Examining Shared Memory</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/examining-shared-memory/m-p/4943725#M412184</link>
      <description>shminfo will show you the addresses of all the shared memory segments, but to actually display the contents of a segment, you'll need a program. As you might expect, there are pieces of information needed (from the program creating the segment) to allow access and to prevent unauthorized access from casual users.</description>
      <pubDate>Wed, 30 Nov 2005 21:35:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/examining-shared-memory/m-p/4943725#M412184</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2005-11-30T21:35:05Z</dc:date>
    </item>
    <item>
      <title>Re: Examining Shared Memory</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/examining-shared-memory/m-p/4943726#M412185</link>
      <description>Bear in mind that another approach to actually examining shmem is using Perl. The functions shmget, shmctl, shmread, and shmwrite are all available --- which is rather amazing for a scripting language. One of the obvious problems with a utility that reads shared memory is that the data really only has meaning for its intended  application. The data generally are non-textual. One approach would be to use shmread to read the entire contents of a shared memory segment and write it to a file. You would then use a standard utility like od to examine the file.&lt;BR /&gt;&lt;BR /&gt;The other obvious "gotcha" is that shared memory segments created with IPC_PRIVATE will not be accessible by unrelated processes.</description>
      <pubDate>Wed, 30 Nov 2005 22:23:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/examining-shared-memory/m-p/4943726#M412185</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2005-11-30T22:23:29Z</dc:date>
    </item>
    <item>
      <title>Re: Examining Shared Memory</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/examining-shared-memory/m-p/4943727#M412186</link>
      <description>Thanks for all of the quick responses.  Looks like perl might be the way to go.&lt;BR /&gt;&lt;BR /&gt;Scott</description>
      <pubDate>Thu, 01 Dec 2005 10:14:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/examining-shared-memory/m-p/4943727#M412186</guid>
      <dc:creator>OldSchool</dc:creator>
      <dc:date>2005-12-01T10:14:19Z</dc:date>
    </item>
  </channel>
</rss>

