Changes between Version 2 and Version 3 of TraceMerge


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

--

Legend:

Unmodified
Added
Removed
Modified
  • TraceMerge

    v2 v3  
    1111
    1212=== Applications ===
    13 ==== Concatenating Traces ====
     13==== Concatenating traces ====
    1414{{{
    1515tracemerge erf:merged_trace.gz erf:small_traces-*.gz
     
    2020tracemerge -i erf:merged_trace.gz erf:outgoing.gz erf:incoming.gz
    2121}}}
    22 '''Note:''' most libtrace applications regard a direction of 0 as outgoing and a direction of 1 as incoming, so be sure to specify the input URIs the correct way around
     22'''Note:''' most libtrace applications regard a direction of 0 as outgoing and a direction of 1 as incoming, so be sure to specify the input URIs in the correct order.
    2323
    2424=== Notes ===
    25 {{{tracemerge}}} always produces traces where the packets are in timestamp order
     25 * The output trace format does not have to match the input formats, e.g. {{{tracemerge pcapfile:merged_trace.pcap.gz erf:small_traces-*.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.
     26 * As the name implies, {{{tracemerge}}} will produce a trace where the packets are all in timestamp order.