<?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 Tracing Sockets based comms on single server in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/tracing-sockets-based-comms-on-single-server/m-p/2464294#M15263</link>
    <description>I have looked at most of the recommended utilities, but cannot find something which doesnt rely on actual traffic crossing a machine boundary. Our app uses unix domain sockets to implement inter-process comms on the one server (HPUX 11). Is there a way to fool, say, TCPDUMP, into seeing this traffic ?&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
    <pubDate>Mon, 13 Nov 2000 12:05:06 GMT</pubDate>
    <dc:creator>Steve Roberts</dc:creator>
    <dc:date>2000-11-13T12:05:06Z</dc:date>
    <item>
      <title>Tracing Sockets based comms on single server</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tracing-sockets-based-comms-on-single-server/m-p/2464294#M15263</link>
      <description>I have looked at most of the recommended utilities, but cannot find something which doesnt rely on actual traffic crossing a machine boundary. Our app uses unix domain sockets to implement inter-process comms on the one server (HPUX 11). Is there a way to fool, say, TCPDUMP, into seeing this traffic ?&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Mon, 13 Nov 2000 12:05:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tracing-sockets-based-comms-on-single-server/m-p/2464294#M15263</guid>
      <dc:creator>Steve Roberts</dc:creator>
      <dc:date>2000-11-13T12:05:06Z</dc:date>
    </item>
    <item>
      <title>Re: Tracing Sockets based comms on single server</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tracing-sockets-based-comms-on-single-server/m-p/2464295#M15264</link>
      <description>perhaps etheral gives you a view&lt;BR /&gt;&lt;A href="http://hpux.cs.utah.edu/hppd/hpux/Gtk/ethereal-0.8.11/" target="_blank"&gt;http://hpux.cs.utah.edu/hppd/hpux/Gtk/ethereal-0.8.11/&lt;/A&gt;</description>
      <pubDate>Mon, 13 Nov 2000 12:16:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tracing-sockets-based-comms-on-single-server/m-p/2464295#M15264</guid>
      <dc:creator>Rainer_1</dc:creator>
      <dc:date>2000-11-13T12:16:59Z</dc:date>
    </item>
    <item>
      <title>Re: Tracing Sockets based comms on single server</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tracing-sockets-based-comms-on-single-server/m-p/2464296#M15265</link>
      <description>In order to trace all packets sent by node and addressed to node : &lt;BR /&gt;&lt;BR /&gt;1) start trace putting data into 1MB trace file ( /tmp/raw.TRC0, raw.TRC1). &lt;BR /&gt;/etc/nettl -tn -pduin -pduout -e all -f /tmp/raw &lt;BR /&gt;&lt;BR /&gt;2) stop trace -&amp;gt; /etc/nettl -tf -e all &lt;BR /&gt;3) Format traces into a file like this : &lt;BR /&gt;&lt;BR /&gt;/etc/netfmt -N -n -l -f /tmp/raw.TRC0 &amp;gt; /tmp/file0 &lt;BR /&gt;&lt;BR /&gt;/etc/netfmt -N -n -l -f /tmp/raw.TRC1 &amp;gt; /tmp/file1 &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;-n option -&amp;gt; print IP addresses, not hostnames &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I hope this helps &lt;BR /&gt;&lt;BR /&gt;Federico</description>
      <pubDate>Mon, 13 Nov 2000 15:07:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tracing-sockets-based-comms-on-single-server/m-p/2464296#M15265</guid>
      <dc:creator>federico_3</dc:creator>
      <dc:date>2000-11-13T15:07:40Z</dc:date>
    </item>
  </channel>
</rss>

