Date: Sun, 11 Apr 2004 11:27:11 +0200 From: "Knocke" <knockefreebsd@o2.pl> To: <freebsd-net@freebsd.org> Subject: Re: [nwebe] How to track TCP socket variables? (cwnd, ssthresh) Message-ID: <003101c41fa7$2cb9cc70$df5561d9@ALFA> References: <001901c41eee$3f09c0b0$df5561d9@ALFA> <20040410120027.GC710@empiric.dek.spc.org> <003901c41f02$b31ec3b0$df5561d9@ALFA> <4077FE82.7040308@netli.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Yes, the application must use setsockopt() call to enable socket debugging. > If an application does not turn it on, you can create a simple library > which would substitute socket() with socket()+setsockopt(SO_DEBUG) pair, > and attach it to the application via LD_PRELOAD. uhmm, ok. I'd like to check it first on any socket, do you know any network programms (aplications, benchmarks etc) to open sockets with debug option, or give a '-'switch to do that? trpt on my system keeps on saying : % trpt: /boot/kernel/kernel: no namelist so probably no sockets are currently SO_DEBUG ready. hk
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?003101c41fa7$2cb9cc70$df5561d9>