<?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: Cannot match up PID's with TCP/IP sockets using netstat... in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/cannot-match-up-pid-s-with-tcp-ip-sockets-using-netstat/m-p/3531623#M221574</link>
    <description>Try lsof,&lt;BR /&gt;&lt;A href="ftp://vic.cc.purdue.edu/pub/tools/unix/lsof/" target="_blank"&gt;ftp://vic.cc.purdue.edu/pub/tools/unix/lsof/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;cheers</description>
    <pubDate>Mon, 25 Apr 2005 16:05:10 GMT</pubDate>
    <dc:creator>Robert Salter</dc:creator>
    <dc:date>2005-04-25T16:05:10Z</dc:date>
    <item>
      <title>Cannot match up PID's with TCP/IP sockets using netstat...</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cannot-match-up-pid-s-with-tcp-ip-sockets-using-netstat/m-p/3531622#M221573</link>
      <description>Hi gang,&lt;BR /&gt;&lt;BR /&gt;I'm running HP-UX 11.11 and am having a problem trying to match up PID's with the TCP/IP socket that it was initiated from.&lt;BR /&gt;&lt;BR /&gt;I also have a Linux server here whose netstat command uses the -p option much differently than HP-UX's netstat does.  On Linux, the -p option shows the PID and name of the program to which each socket belongs.&lt;BR /&gt;&lt;BR /&gt;This is exactly what I'm looking for.  Is there a newer binary set for netstat that I need to download and install on my HP-UX server, or is there another way of retrieving this information?&lt;BR /&gt;&lt;BR /&gt;Any insight would be greatly appreciated!&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;Rick</description>
      <pubDate>Mon, 25 Apr 2005 15:59:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cannot-match-up-pid-s-with-tcp-ip-sockets-using-netstat/m-p/3531622#M221573</guid>
      <dc:creator>Rick Braman</dc:creator>
      <dc:date>2005-04-25T15:59:27Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot match up PID's with TCP/IP sockets using netstat...</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cannot-match-up-pid-s-with-tcp-ip-sockets-using-netstat/m-p/3531623#M221574</link>
      <description>Try lsof,&lt;BR /&gt;&lt;A href="ftp://vic.cc.purdue.edu/pub/tools/unix/lsof/" target="_blank"&gt;ftp://vic.cc.purdue.edu/pub/tools/unix/lsof/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;cheers</description>
      <pubDate>Mon, 25 Apr 2005 16:05:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cannot-match-up-pid-s-with-tcp-ip-sockets-using-netstat/m-p/3531623#M221574</guid>
      <dc:creator>Robert Salter</dc:creator>
      <dc:date>2005-04-25T16:05:10Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot match up PID's with TCP/IP sockets using netstat...</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cannot-match-up-pid-s-with-tcp-ip-sockets-using-netstat/m-p/3531624#M221575</link>
      <description>Hi Rick,&lt;BR /&gt;lsof will fulfill your task, but you have a problems  installing from the depot. You have to recompile it on your machine.&lt;BR /&gt;Regards,&lt;BR /&gt;Borislav</description>
      <pubDate>Tue, 26 Apr 2005 04:36:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cannot-match-up-pid-s-with-tcp-ip-sockets-using-netstat/m-p/3531624#M221575</guid>
      <dc:creator>Borislav Perkov</dc:creator>
      <dc:date>2005-04-26T04:36:26Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot match up PID's with TCP/IP sockets using netstat...</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cannot-match-up-pid-s-with-tcp-ip-sockets-using-netstat/m-p/3531625#M221576</link>
      <description>Indeed, -p on HP-UX netstat is (properly, IMO :) :) :) for specifying a protocol and getting its statistics.&lt;BR /&gt;&lt;BR /&gt;If and when you see output in netstat -an with no corresponding entry in lsof output, check ndd /dev/tcp tcp_status - the entries with "*" after the TCP state mean they have no associated socket/process and so would not appear in lsof output.&lt;BR /&gt;&lt;BR /&gt;Examples would be TIME_WAIT's, and perhaps any of the FIN_WAIT states.  Even ESTABLISHED is possible - for connections that have been established, but for which accept() has yet to be called.&lt;BR /&gt;</description>
      <pubDate>Tue, 26 Apr 2005 11:53:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cannot-match-up-pid-s-with-tcp-ip-sockets-using-netstat/m-p/3531625#M221576</guid>
      <dc:creator>rick jones</dc:creator>
      <dc:date>2005-04-26T11:53:37Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot match up PID's with TCP/IP sockets using netstat...</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cannot-match-up-pid-s-with-tcp-ip-sockets-using-netstat/m-p/3531626#M221577</link>
      <description>lsof will show an install error and then be usable. You can manually set suid on one file it complains about and it will be totally usable.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Tue, 26 Apr 2005 12:06:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cannot-match-up-pid-s-with-tcp-ip-sockets-using-netstat/m-p/3531626#M221577</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2005-04-26T12:06:51Z</dc:date>
    </item>
  </channel>
</rss>

