TRACEMERGE(1)
NAME
tracemerge - Merge one (or more) traces together
SYNOPSIS
tracemerge [ -i [ interfaces_per_input ] | --set-interface [ inter- faces_per_input ] ] [ -u | --unique-packets ] 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.
- -z[compression_level]
--compression[compression_level] - Sets the amount of compression performed on the output file. Currently libtrace will always write out compressed files, even when -z0 is given.
LINKS
More details about tracemerge (and libtrace) can be found at
http://www.wand.net.nz/trac/libtrace/wiki/UserDocumentation
SEE ALSO
libtrace(3), tracesplit(1), tracesplit_dir(1), tracefilter(1), traceconvert(1), tracereport(1), tracertstats(1), tracestats(1), tracedump(1), traceanon(1), tracesummary(1)
AUTHORS
- Perry Lorier <perry@cs.waikato.ac.nz>