From: Jose Manuel Cano Garcia <cano@pc2072te.dte.uma.es> Subject: Re: tcptrace Feature Request Date: Tue, 17 Sep 2002 16:21:52 +0200 Message-Id: <200209171621.52741.cano@pc2072te.dte.uma.es>
Hi,
I prefer only one line per connection, too. As I said in my previous mail, I'm
interested in procesing the traces wiht mathlab. In the modified source code
I sent several days ago, I selected this simpler option. Another sugestion is
the possibility of optionally printing the IP address in hexadecimal rather
than in typical "dot" format, and the hour by means of the second and
microsecond fields (rather than day, hour, minute, second.....)
Other important thing are the output messages. I had to modify the code (not
only output.c) in order to prevent several warning and informational messages
from going to the stdout output. I prefer to send them to stderr output, so
when you redirect stdout to a file, these messages do not go to the trace
file. These messages makes more dificult to load directly a trace file.
Best regards,
Jose Manuel
PD: Excuse me for sugesting too much....
El Mar 17 Sep 2002 13:25, Mark Allman escribió:
> I'll put in my vote for the connection summary being all on one
> line. Connections are easier to deal with in perl or awk when
> they're a line at a time, rather than being required to pick over N
> lines (of which you only care about a couple, probably) before you
> have all the information about a connection. IMO, putting
> everything on multiple lines, just with commas now, is not so useful
> (because the parsing of the lines is not the biggest pain -- it's
> the gathering of things). YMMV.
>
> allman
----------------------------------------------------------------------------
To unsubscribe, send a message with body containing "unsubscribe tcptrace" to
majordomo@tcptrace.org.
This archive was generated by hypermail 2b30 : 09/17/02 EDT