| 1 | .TH TRACEMERGE "1" "March 2006" "tracemerge (libtrace)" "User Commands" |
|---|
| 2 | .SH NAME |
|---|
| 3 | tracemerge \- Merge one (or more) traces together |
|---|
| 4 | .SH SYNOPSIS |
|---|
| 5 | .B tracemerge |
|---|
| 6 | [ \-i [ interfaces_per_input ] | \-\^\-set-interface [ interfaces_per_input ] ] |
|---|
| 7 | [ \-u | \-\^\-unique-packets ] [ \-z | \-\^\-compress-level <level> ] |
|---|
| 8 | [ \-Z | \-\^\-compress-type <method> ] |
|---|
| 9 | outputuri inputuri... |
|---|
| 10 | .SH DESCRPTION |
|---|
| 11 | tracemerge merges two or more traces together, keeping packets in order. |
|---|
| 12 | |
|---|
| 13 | .TP |
|---|
| 14 | .PD 0 |
|---|
| 15 | .BI \-i [ interfaces_per_input ] |
|---|
| 16 | .TP |
|---|
| 17 | .PD |
|---|
| 18 | .BI \-\^\-set-interface [interfaces_per_input ] |
|---|
| 19 | set the interface ("direction") for each input to be unique. The optional |
|---|
| 20 | inputs_per_interface parameter is how many inputs to reserve for each trace, |
|---|
| 21 | and defaults to 1. Thus if you have two traces with two interfaces (in/out), |
|---|
| 22 | and interfaces_per_input is set to 2, then tracemerge will have the first |
|---|
| 23 | interface of the first input will be 0, the second interface of the first input |
|---|
| 24 | will be 1, the first interface of the second input will be 2, and the second |
|---|
| 25 | interface of the second input will be 3. |
|---|
| 26 | |
|---|
| 27 | Beware that erf only supports 4 interfaces, and pcap only supports 2. |
|---|
| 28 | Limitations apply based on the input trace format (not the output trace format) |
|---|
| 29 | |
|---|
| 30 | .TP |
|---|
| 31 | .PD 0 |
|---|
| 32 | .BI \-u |
|---|
| 33 | .TP |
|---|
| 34 | .PD |
|---|
| 35 | .BI \-\^\-unique-packets |
|---|
| 36 | Ignore duplicate packets with identical timestamps. |
|---|
| 37 | |
|---|
| 38 | .TP |
|---|
| 39 | .PD 0 |
|---|
| 40 | .BI \-z level |
|---|
| 41 | .TP |
|---|
| 42 | .PD |
|---|
| 43 | .BI \-\^\-compress-level level |
|---|
| 44 | Sets the amount of compression performed on the output file. This value can |
|---|
| 45 | range from 0 (no compression) to 9 (maximum compression). Higher compression |
|---|
| 46 | levels require more CPU to compress data. Defaults to 0. |
|---|
| 47 | |
|---|
| 48 | .TP |
|---|
| 49 | .PD 0 |
|---|
| 50 | .BI \-Z method |
|---|
| 51 | .TP |
|---|
| 52 | .PD |
|---|
| 53 | .BI \-\^\-compress-type method |
|---|
| 54 | Describes the compression algorithm to be used when writing the output trace. |
|---|
| 55 | Possible methods are "gz", "bz", "lzo", "xz" and "no". Defaults to |
|---|
| 56 | "no". |
|---|
| 57 | |
|---|
| 58 | |
|---|
| 59 | .SH LINKS |
|---|
| 60 | More details about tracemerge (and libtrace) can be found at |
|---|
| 61 | http://www.wand.net.nz/trac/libtrace/wiki/UserDocumentation |
|---|
| 62 | |
|---|
| 63 | .SH SEE ALSO |
|---|
| 64 | libtrace(3), tracesplit(1), tracesplit_dir(1), tracefilter(1), |
|---|
| 65 | traceconvert(1), tracereport(1), tracertstats(1), tracestats(1), |
|---|
| 66 | tracepktdump(1), traceanon(1), tracesummary(1), tracereplay(1), |
|---|
| 67 | tracediff(1), traceends(1), tracetopends(1) |
|---|
| 68 | |
|---|
| 69 | .SH AUTHORS |
|---|
| 70 | Perry Lorier <perry@cs.waikato.ac.nz> |
|---|
