Changes between Version 4 and Version 5 of TraceMerge


Ignore:
Timestamp:
02/27/07 11:53:22 (14 years ago)
Author:
spa1
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TraceMerge

    v4 v5  
    2323
    2424=== Notes ===
    25  * The output trace format does not have to match the input formats, e.g. {{{tracemerge pcapfile:merged_trace.pcap.gz erf:small_traces-1.gz erf:small_traces-2.gz}}} will work. There is also no requirement for the input traces to all be of the same format either. These properties hold true for all libtrace applications, although format header information can be lost converting from one format to another, e.g. pcap headers have no space to store the ERF rxerror variable.
     25 * The output trace format does not have to match the input formats, e.g.
     26{{{
     27tracemerge pcapfile:merged_trace.pcap.gz erf:small_traces-1.gz erf:small_traces-2.gz
     28}}}
     29   will work. There is also no requirement for the input traces to all be of the same format either. These properties hold true for all libtrace applications, although format header information can be lost converting from one format to another, e.g. pcap headers have no space to store the ERF rxerror variable.
    2630 * As the name implies, {{{tracemerge}}} will produce a trace where the packets are all in timestamp order.