Re^2: Ip trace on lo0 Solaris

tirwhan,

can you give me some examples of how to use truss for tracing communication of processes using loopback? thx

Comment on Re^2: Ip trace on lo0 Solaris

Replies are listed 'Best First'.
Re^3: Ip trace on lo0 Solaris by tirwhan (Abbot) on Feb 03, 2006 at 17:04 UTC
You'll have to read your system's man-pages for specifics, I don't have a Solaris system handy. In general you'd Find the PID of the process communicating over loopback which you are interested in. You can use netstat for this, e.g. on Linux `netstat -nlp --tcp \| grep '127\.0\.0\.1'` will show you all processes listening on the loopback IP for TCP connections. Run truss with the appropriate option to show network system calls with their full argument strings. Using strace (the Linux equivalent to truss) this can be done with `strace -p <pid> -e trace=network -s 65536` All dogma is stupid.	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^3: Ip trace on lo0 Solaris
by tirwhan (Abbot) on Feb 03, 2006 at 17:04 UTC

You'll have to read your system's man-pages for specifics, I don't have a Solaris system handy. In general you'd

Find the PID of the process communicating over loopback which you are interested in. You can use netstat for this, e.g. on Linux
netstat -nlp --tcp | grep '127\.0\.0\.1'
will show you all processes listening on the loopback IP for TCP connections.
Run truss with the appropriate option to show network system calls with their full argument strings. Using strace (the Linux equivalent to truss) this can be done with
strace -p <pid> -e trace=network -s 65536

All dogma is stupid.