<?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 Samx process in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/samx-process/m-p/2648143#M45398</link>
    <description>Hello,&lt;BR /&gt;&lt;BR /&gt;There is a process called samx running on our server which is using all the resources of the CPU. The moment I kill it, another processes with username root / command samx is started. I know that samx is part of sam and contains the libraries. If somebody could advise...thanks.&lt;BR /&gt;&lt;BR /&gt;Frederic.</description>
    <pubDate>Fri, 18 Jan 2002 08:14:07 GMT</pubDate>
    <dc:creator>Frederic Serre</dc:creator>
    <dc:date>2002-01-18T08:14:07Z</dc:date>
    <item>
      <title>Samx process</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/samx-process/m-p/2648143#M45398</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;There is a process called samx running on our server which is using all the resources of the CPU. The moment I kill it, another processes with username root / command samx is started. I know that samx is part of sam and contains the libraries. If somebody could advise...thanks.&lt;BR /&gt;&lt;BR /&gt;Frederic.</description>
      <pubDate>Fri, 18 Jan 2002 08:14:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/samx-process/m-p/2648143#M45398</guid>
      <dc:creator>Frederic Serre</dc:creator>
      <dc:date>2002-01-18T08:14:07Z</dc:date>
    </item>
    <item>
      <title>Re: Samx process</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/samx-process/m-p/2648144#M45399</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;You will probably find that the 'samx'&lt;BR /&gt;process has lost it's parent and therefore&lt;BR /&gt;become owned by init. The answer is &lt;BR /&gt;before attempting to kill it, make sure&lt;BR /&gt;that no other user tries to start a sam&lt;BR /&gt;session, and make sure that any associated&lt;BR /&gt;processes for 'samx' are killed off at the&lt;BR /&gt;same time.&lt;BR /&gt;&lt;BR /&gt;-Michael</description>
      <pubDate>Fri, 18 Jan 2002 08:23:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/samx-process/m-p/2648144#M45399</guid>
      <dc:creator>Michael Tully</dc:creator>
      <dc:date>2002-01-18T08:23:34Z</dc:date>
    </item>
    <item>
      <title>Re: Samx process</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/samx-process/m-p/2648145#M45400</link>
      <description>&lt;BR /&gt;check the parent process of the samx process, this is probably whats restarting it. Kill the parent first, then the samx process.</description>
      <pubDate>Fri, 18 Jan 2002 08:34:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/samx-process/m-p/2648145#M45400</guid>
      <dc:creator>Stefan Farrelly</dc:creator>
      <dc:date>2002-01-18T08:34:20Z</dc:date>
    </item>
  </channel>
</rss>

