Hi Anand,
I did what you said but i am getting a strange output
[root@machine0 Desktop]#ls
cli trace.dat.cpu11 trace.dat.cpu2 trace.dat.cpu7
client.c trace.dat.cpu12 trace.dat.cpu3 trace.dat.cpu8
trace.dat.cpu0 trace.dat.cpu13 trace.dat.cpu4 trace.dat.cpu9
This helps me to see the forest for the trees. And it’s pretty current:
http://upload.wikimedia.org/wikipedia/commons/3/37/Netfilter-packet-flow.svg
Jeff Haran
From: kernelnewbies-boun...@kernelnewbies.org
[mailto:kernelnewbies-boun...@kernelnewbies.org] On Behalf Of Anil Joshi
Sent: Tuesday,
Hi Anil,
You need to use trace-cmd record command and run you client. For example.
I chose to write a tcp simple client server application.
Server running on remote machine listening on some port
I executed below command to connect to the server using trace-cmd record
Below command records all
a 'slightly' more indepth look:
http://www.linuxfoundation.org/images/1/1c/Network_data_flow_through_kernel.png
kind regards
anupam
On Tue, Jul 15, 2014 at 10:33 PM, Jeff Haran jeff.ha...@citrix.com wrote:
This helps me to see the forest for the trees. And it's pretty current:
