tracemerge1
Merge one (or more) traces together
Usage
tracemerge [{-i
[interfaces_per_input] | --set-interface
[interfaces_per_input]}]
[{-u | --unique-packets}]
[{-z | --compress-level
<level>}]
[{-Z | --compress-type
<method>}]
outputuri
inputuri ...
Descrption
tracemerge merges two or more traces together, keeping packets in order.
-i[interfaces_per_input]
--set-interface[interfaces_per_input]-
set the interface ("direction") for each input to be unique. The optional inputs_per_interface parameter is how many inputs to reserve for each trace, and defaults to 1. Thus if you have two traces with two interfaces (in/out), and interfaces_per_input is set to 2, then tracemerge will have the first interface of the first input will be 0, the second interface of the first input will be 1, the first interface of the second input will be 2, and the second interface of the second input will be 3.
Beware that erf only supports 4 interfaces, and pcap only supports 2. Limitations apply based on the input trace format (not the output trace format)
-u
--unique-packets-
Ignore duplicate packets with identical timestamps.
-zlevel
--compress-levellevel-
Sets the amount of compression performed on the output file. This value can range from 0 (no compression) to 9 (maximum compression). Higher compression levels require more CPU to compress data. Defaults to 0.
-Zmethod
--compress-typemethod-
Describes the compression algorithm to be used when writing the output trace. Possible methods are "gzip", "bzip2", "lzo", "xz" and "none". Defaults to "none".
Links
More details about tracemerge (and libtrace) can be found at http://www.wand.net.nz/trac/libtrace/wiki/UserDocumentation
Releases
9 releases since Debian 5.0 (Lenny); the text changed 3 times.