Hello,
This is a rather odd bug/weird behavior. Confidence is high that it is not
logic in my code this time. Please read the following carefully!
In a web-crawling program I am writing, I deal with several thousand fds at
a time. I am using FreeBSD's KQueue to keep track of them all so that I
Dear networkers,
Like I mumbled in another email, I've started working on a small
project that (when done) will allow for a per-interface polling(4)
status to be changed in run-time. Attached is a proof of the
concept patch, that currently has support for the dc(4) driver
only (basically because
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
aplicat
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
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
Hi!
I'm about to get a bit deeper into TCP world, recently experienced a problem - I need
to have a real-time image of actual active TCP socket state, its most important
variables like: cwnd, ssthresh, S and R windows, etc,
I thought I'd be possible to see using tcpdump, but as far as I know it
