<?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 System Call Tracing in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/system-call-tracing/m-p/2601141#M855783</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;does anybody out there know a tool to log all(!) system-calls over all(!) processes?&lt;BR /&gt;&lt;BR /&gt;Tusc won't do this job because it only logs one process. With glance I can see the calls but I can't see which process did start them.&lt;BR /&gt;&lt;BR /&gt;Frank&lt;BR /&gt;</description>
    <pubDate>Thu, 25 Oct 2001 07:44:09 GMT</pubDate>
    <dc:creator>Frank Gilsdorf</dc:creator>
    <dc:date>2001-10-25T07:44:09Z</dc:date>
    <item>
      <title>System Call Tracing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-call-tracing/m-p/2601141#M855783</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;does anybody out there know a tool to log all(!) system-calls over all(!) processes?&lt;BR /&gt;&lt;BR /&gt;Tusc won't do this job because it only logs one process. With glance I can see the calls but I can't see which process did start them.&lt;BR /&gt;&lt;BR /&gt;Frank&lt;BR /&gt;</description>
      <pubDate>Thu, 25 Oct 2001 07:44:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-call-tracing/m-p/2601141#M855783</guid>
      <dc:creator>Frank Gilsdorf</dc:creator>
      <dc:date>2001-10-25T07:44:09Z</dc:date>
    </item>
    <item>
      <title>Re: System Call Tracing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-call-tracing/m-p/2601142#M855784</link>
      <description>Hi, &lt;BR /&gt;&lt;BR /&gt;try with 'trace'&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 25 Oct 2001 08:07:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-call-tracing/m-p/2601142#M855784</guid>
      <dc:creator>Ravi_8</dc:creator>
      <dc:date>2001-10-25T08:07:22Z</dc:date>
    </item>
    <item>
      <title>Re: System Call Tracing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-call-tracing/m-p/2601143#M855785</link>
      <description>You should be able to use tusc to trace system calls.  You can get tusc from the porting center:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://hpux.connect.org.uk/hppd/hpux/Sysadmin/tusc-7.0/" target="_blank"&gt;http://hpux.connect.org.uk/hppd/hpux/Sysadmin/tusc-7.0/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;If you need something for HPUX 10.x then you would have to get trace, also available from the porting center:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://hpux.connect.org.uk/hppd/hpux/Sysadmin/trace-1.6/" target="_blank"&gt;http://hpux.connect.org.uk/hppd/hpux/Sysadmin/trace-1.6/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;-Santosh</description>
      <pubDate>Thu, 25 Oct 2001 08:36:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-call-tracing/m-p/2601143#M855785</guid>
      <dc:creator>Santosh Nair_1</dc:creator>
      <dc:date>2001-10-25T08:36:22Z</dc:date>
    </item>
    <item>
      <title>Re: System Call Tracing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-call-tracing/m-p/2601144#M855786</link>
      <description>Sorry,&lt;BR /&gt;&lt;BR /&gt;tusc won't do the job. I wan't to start the tracer and it has to log all actuall processes and the processes that will start in future.&lt;BR /&gt;&lt;BR /&gt;I've heard on SGI padc will do this. Can I find something similar on HP-UX?&lt;BR /&gt;&lt;BR /&gt;Frank</description>
      <pubDate>Thu, 25 Oct 2001 10:23:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-call-tracing/m-p/2601144#M855786</guid>
      <dc:creator>Frank Gilsdorf</dc:creator>
      <dc:date>2001-10-25T10:23:44Z</dc:date>
    </item>
    <item>
      <title>Re: System Call Tracing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-call-tracing/m-p/2601145#M855787</link>
      <description>Frank,&lt;BR /&gt;&lt;BR /&gt;   I once used a tool similar to what&lt;BR /&gt;you are looking for- logging all system calls,&lt;BR /&gt;snapshots of the system activity etc -&lt;BR /&gt;which was given by a HP performance expert&lt;BR /&gt;for diagonsing a performance problem.&lt;BR /&gt;I don't remember the name of the tool,&lt;BR /&gt;but it used to produce ouput in the order&lt;BR /&gt;of &amp;gt;500Mb in a matter of few minutes and&lt;BR /&gt;we used to run it only for a short while.&lt;BR /&gt;&lt;BR /&gt;    Another option you have is&lt;BR /&gt;to run  truss  with the  -p option.&lt;BR /&gt;truss -p &lt;PID&gt; ;  To check all the processes&lt;BR /&gt;running on the system, put  ps command in&lt;BR /&gt;a loop, grab any new process id and run&lt;BR /&gt;truss on it.   But, i understand it can&lt;BR /&gt;get clumsy with lots of truss commands running.&lt;BR /&gt;&lt;BR /&gt;  I will try to remember the HP tool and&lt;BR /&gt;post back.&lt;BR /&gt;&lt;BR /&gt;-raj&lt;BR /&gt;&lt;BR /&gt;&lt;/PID&gt;</description>
      <pubDate>Thu, 25 Oct 2001 10:35:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-call-tracing/m-p/2601145#M855787</guid>
      <dc:creator>Roger Baptiste</dc:creator>
      <dc:date>2001-10-25T10:35:00Z</dc:date>
    </item>
    <item>
      <title>Re: System Call Tracing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-call-tracing/m-p/2601146#M855788</link>
      <description>Okay, how about this tool from HP called prospect...its supposed to monitor all system calls.  One caveat though, the log files can grow rapidly especially on a busy system:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="ftp://ftp.cup.hp.com/dist/networking/tools/prospect/" target="_blank"&gt;ftp://ftp.cup.hp.com/dist/networking/tools/prospect/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;-Santosh</description>
      <pubDate>Thu, 25 Oct 2001 11:15:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-call-tracing/m-p/2601146#M855788</guid>
      <dc:creator>Santosh Nair_1</dc:creator>
      <dc:date>2001-10-25T11:15:13Z</dc:date>
    </item>
    <item>
      <title>Re: System Call Tracing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-call-tracing/m-p/2601147#M855789</link>
      <description>Frank,&lt;BR /&gt;&lt;BR /&gt;I think Glance has PROCSYSCALL_??_?? types of metrics that you can use.  Depending on what kind of a report you would like to generate, you could tailor your adviser syntax accordingly.  I've attached an example.  To see a sample of the report, save the attached file to, say, sc.syntax in your current directory; then run:&lt;BR /&gt;&lt;BR /&gt;glance -adviser_only -syntax sc.syntax -iterations 3 | tail +20 &amp;gt; glance.out&lt;BR /&gt;&lt;BR /&gt;Is the output file glance.out something like what you want to see?   &lt;BR /&gt;&lt;BR /&gt;Mladen</description>
      <pubDate>Thu, 25 Oct 2001 17:57:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-call-tracing/m-p/2601147#M855789</guid>
      <dc:creator>Mladen Despic</dc:creator>
      <dc:date>2001-10-25T17:57:58Z</dc:date>
    </item>
  </channel>
</rss>

