From: aoeu thaoteuf (aoeu4@hotmail.com)
Date: 10/24/03
From: "aoeu thaoteuf" <aoeu4@hotmail.com> Subject: Worst tcptrace 'feature' Date: Fri, 24 Oct 2003 10:39:51 +0000 Message-ID: <BAY2-F118JSFsxf4yp80001cf41@hotmail.com>
I have started using tcptrace recently, and find it an
interesting tool.
There is however one very big bug - which I see gets touted as a
feature. This is the insistance that TCP connections be considered
timed-out after 4 minutes.
This is sheer lunacy, especially for saved trace files - and is probably
the feature witch shed the most negative light on tcptrace thus
far for me.
Furthermore it does not even appear to be well documented. First
I saw of it was trawling through the mail archives.
Certainly, if you insist on keeping a feature which causes traces
to be misrepresented by tcptrace, you should put it in the FAQ,
or somewhere quite prominent? Perhaps also have the default
value for --nonreal_live_conn_interval set to infinity.
Apologies for getting carried away like this. I quite like what I
have seen of tcptrace thus far - but this feature bit me, and
nearly had me throw tcptrace away in preference to my usual perl
parsing. I really think tcptrace would be a better application if
this feature simply be removed.
I'd be interested to see if any users agree with my sentiments
on this?
_________________________________________________________________
Cheer a special someone with a fun Halloween eCard from American Greetings!
Go to http://www.msn.americangreetings.com/index_msn.pd?source=msne134
----------------------------------------------------------------------------
To unsubscribe, send a message with body containing "unsubscribe tcptrace" to
majordomo@tcptrace.org.
This archive was generated by hypermail 2.1.7 : 10/24/03 EDT