<?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: process in top in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/process-in-top/m-p/3462932#M210413</link>
    <description>sorry - I forgot a few words in my post, I meant to say that You if You do ps -ef | grep &lt;PID&gt; and then do recusively the same for the ppid until it's 1 (init itself), You have built a process tree which exactly shows what spawned the process in question.&lt;BR /&gt;&lt;BR /&gt;unless it's ppid is 1 , in which case You should try grep processname /sbin/init.d/* .&lt;BR /&gt;If it's not there, check out cron jobs or have a look into /etc/inittab.&lt;BR /&gt;&lt;BR /&gt;If this all fails, do a find / -local -name &lt;PROCESSNAME&gt; and search the containing directory for any kind of readme info or logfiles.&lt;BR /&gt;&lt;BR /&gt;best luck, &lt;BR /&gt;florian&lt;/PROCESSNAME&gt;&lt;/PID&gt;</description>
    <pubDate>Thu, 13 Jan 2005 15:22:52 GMT</pubDate>
    <dc:creator>Florian Heigl (new acc)</dc:creator>
    <dc:date>2005-01-13T15:22:52Z</dc:date>
    <item>
      <title>process in top</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/process-in-top/m-p/3462930#M210411</link>
      <description>I have series of ps processes in top but I am not able to find out from where it is getting triggered, tty field in top shows ?. so how can I foun dout from where this ps is getting generated, &amp;amp; eating considerable cpu.</description>
      <pubDate>Thu, 13 Jan 2005 13:59:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/process-in-top/m-p/3462930#M210411</guid>
      <dc:creator>vaman</dc:creator>
      <dc:date>2005-01-13T13:59:24Z</dc:date>
    </item>
    <item>
      <title>Re: process in top</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/process-in-top/m-p/3462931#M210412</link>
      <description>doing a ps -ef | grep pid until the ppid (parent process id) will help You work through to the process that spawned Your cpu eaters.&lt;BR /&gt;&lt;BR /&gt;some systems also have pstree available, which does the very same thing in a nicer, graphical way.</description>
      <pubDate>Thu, 13 Jan 2005 14:03:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/process-in-top/m-p/3462931#M210412</guid>
      <dc:creator>Florian Heigl (new acc)</dc:creator>
      <dc:date>2005-01-13T14:03:25Z</dc:date>
    </item>
    <item>
      <title>Re: process in top</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/process-in-top/m-p/3462932#M210413</link>
      <description>sorry - I forgot a few words in my post, I meant to say that You if You do ps -ef | grep &lt;PID&gt; and then do recusively the same for the ppid until it's 1 (init itself), You have built a process tree which exactly shows what spawned the process in question.&lt;BR /&gt;&lt;BR /&gt;unless it's ppid is 1 , in which case You should try grep processname /sbin/init.d/* .&lt;BR /&gt;If it's not there, check out cron jobs or have a look into /etc/inittab.&lt;BR /&gt;&lt;BR /&gt;If this all fails, do a find / -local -name &lt;PROCESSNAME&gt; and search the containing directory for any kind of readme info or logfiles.&lt;BR /&gt;&lt;BR /&gt;best luck, &lt;BR /&gt;florian&lt;/PROCESSNAME&gt;&lt;/PID&gt;</description>
      <pubDate>Thu, 13 Jan 2005 15:22:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/process-in-top/m-p/3462932#M210413</guid>
      <dc:creator>Florian Heigl (new acc)</dc:creator>
      <dc:date>2005-01-13T15:22:52Z</dc:date>
    </item>
    <item>
      <title>Re: process in top</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/process-in-top/m-p/3462933#M210414</link>
      <description>I'm not really focussed today - the job might also have lost it's controlling terminal, e.g. was started from an X login session that abnormally terminated.</description>
      <pubDate>Thu, 13 Jan 2005 15:24:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/process-in-top/m-p/3462933#M210414</guid>
      <dc:creator>Florian Heigl (new acc)</dc:creator>
      <dc:date>2005-01-13T15:24:30Z</dc:date>
    </item>
  </channel>
</rss>

