Re: [nwebe] How to track TCP socket variables? (cwnd, ssthresh)
From: Lev Walkin (vlm_at_netli.com)
Date: 04/10/04
- Previous message: Knocke: "Re: [nwebe] How to track TCP socket variables? (cwnd, ssthresh)"
- In reply to: Knocke: "Re: [nwebe] How to track TCP socket variables? (cwnd, ssthresh)"
- Next in thread: Knocke: "Re: [nwebe] How to track TCP socket variables? (cwnd, ssthresh)"
- Reply: Knocke: "Re: [nwebe] How to track TCP socket variables? (cwnd, ssthresh)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 10 Apr 2004 07:02:42 -0700 To: Knocke <knockefreebsd@o2.pl>
Knocke wrote:
> thanks :-) I must admit that Stevens says sth about that tool.
>
> But there's still (at least) one thing I don't understand: how to enable
> socket debbuging? Is it possible only when socket is created (fe: by some
> special system call) ? If yes, does it mean that it depends on the
> aplication itself, if it opens its sockets for debbuging and/or if it gives
> a command line switch command to turn it on?
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.
> hk
>
>
> ----- Original Message -----
> From: "Bruce M Simpson" <bms@spc.org>
> To: "Knocke" <knockefreebsd@o2.pl>
> Cc: <freebsd-net@freebsd.org>
> Sent: Saturday, April 10, 2004 2:00 PM
> Subject: Re: [nwebe] How to track TCP socket variables? (cwnd, ssthresh)
>
>
>
>>On Sat, Apr 10, 2004 at 01:23:24PM +0200, Knocke wrote:
>>
>>>Could somebode give me hint what to do? Is there any tool to connect to
>
> existing TCP socket and dump its state per each segment sent or received? Or
> any other way to achive the goal? It could be also a kind of dedicated
> benchmark tool (lice ttcp) that comes togehter with what i need, I don't
> necesarly need to track existing sshd or apache owned sockets.
>
>>man 8 trpt
>>
>>BMS
>>_______________________________________________
>>freebsd-net@freebsd.org mailing list
>>http://lists.freebsd.org/mailman/listinfo/freebsd-net
>>To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
>>
>>__________ NOD32 Informacje 1.713 (20040409) __________
>>
>>Wiadomosc zostala sprawdzona przez System Antywirusowy NOD32
>>http://www.nod32.com lub http://www.nod32.pl
>>
>>
>
>
>
> _______________________________________________
> freebsd-net@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
-- Lev Walkin vlm@netli.com _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
- Previous message: Knocke: "Re: [nwebe] How to track TCP socket variables? (cwnd, ssthresh)"
- In reply to: Knocke: "Re: [nwebe] How to track TCP socket variables? (cwnd, ssthresh)"
- Next in thread: Knocke: "Re: [nwebe] How to track TCP socket variables? (cwnd, ssthresh)"
- Reply: Knocke: "Re: [nwebe] How to track TCP socket variables? (cwnd, ssthresh)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]