source: tools/tracemerge/tracemerge.1 @ 38c00dd

4.0.1-hotfixescachetimestampsdevelopdpdk-ndagetsilivelibtrace4ndag_formatpfringrc-4.0.1rc-4.0.2rc-4.0.3rc-4.0.4ringdecrementfixringperformanceringtimestampfixes
Last change on this file since 38c00dd was 17f954f, checked in by Shane Alcock <salcock@…>, 6 years ago

Add LZMA output support to libtrace tools

Add a configuration option for LZMA output as well.

  • Property mode set to 100644
File size: 2.2 KB
Line 
1.TH TRACEMERGE "1" "March 2006" "tracemerge (libtrace)" "User Commands"
2.SH NAME
3tracemerge \- 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> ]
9outputuri inputuri...
10.SH DESCRPTION
11tracemerge 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 ]
19set the interface ("direction") for each input to be unique.  The optional
20inputs_per_interface parameter is how many inputs to reserve for each trace,
21and defaults to 1.  Thus if you have two traces with two interfaces (in/out),
22and interfaces_per_input is set to 2, then tracemerge will have the first
23interface of the first input will be 0, the second interface of the first input
24will be 1, the first interface of the second input will be 2, and the second
25interface of the second input will be 3.
26
27Beware that erf only supports 4 interfaces, and pcap only supports 2.
28Limitations 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
36Ignore duplicate packets with identical timestamps.
37
38.TP
39.PD 0
40.BI \-z level
41.TP
42.PD
43.BI \-\^\-compress-level level
44Sets the amount of compression performed on the output file. This value can
45range from 0 (no compression) to 9 (maximum compression). Higher compression
46levels 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
54Describes the compression algorithm to be used when writing the output trace.
55Possible methods are "gzip", "bzip2", "lzo", "xz" and "none". Defaults to
56"none".
57
58
59.SH LINKS
60More details about tracemerge (and libtrace) can be found at
61http://www.wand.net.nz/trac/libtrace/wiki/UserDocumentation
62
63.SH SEE ALSO
64libtrace(3), tracesplit(1), tracesplit_dir(1), tracefilter(1),
65traceconvert(1), tracereport(1), tracertstats(1), tracestats(1),
66tracepktdump(1), traceanon(1), tracesummary(1), tracereplay(1),
67tracediff(1), traceends(1), tracetopends(1)
68
69.SH AUTHORS
70Perry Lorier <perry@cs.waikato.ac.nz>
Note: See TracBrowser for help on using the repository browser.