Ignore:
Timestamp:
09/05/07 13:50:34 (14 years ago)
Author:
Perry Lorier <perry@…>
Branches:
4.0.1-hotfixes, cachetimestamps, develop, dpdk-ndag, etsilive, getfragoff, help, libtrace4, master, ndag_format, pfring, rc-4.0.1, rc-4.0.2, rc-4.0.3, rc-4.0.4, ringdecrementfix, ringperformance, ringtimestampfixes
Children:
39aa3c7
Parents:
1708aa8
Message:

Allow setting different interfaces_per_input

File:
1 edited

Legend:

Unmodified
Added
Removed
  • tools/tracemerge/tracemerge.1

    r634089d r34e22d1  
    44.SH SYNOPSIS
    55.B tracemerge
    6 [ \-i | \-\^\-set-interface ]
     6[ \-i [ interfaces_per_input ] | \-\^\-set-interface [ interfaces_per_input ] ]
    77[ \-u | \-\^\-unique-packets ]
    88outputuri inputuri...
     
    1212.TP
    1313.PD 0
    14 .BI \-i
     14.BI \-i [ interfaces_per_input ]
    1515.TP
    1616.PD
    17 .BI \-\^\-set-interface
    18 replace the "interface" bits in the erf header (or the "direction" bit in
    19 other trace files) to be 0 for the first file, 1 for the second file etc.
     17.BI \-\^\-set-interface [interfaces_per_input ]
     18set the interface ("direction") for each input to be unique.  The optional
     19inputs_per_interface parameter is how many inputs to reserve for each trace,
     20and defaults to 1.  Thus if you have two traces with two interfaces (in/out),
     21and interfaces_per_input is set to 2, then tracemerge will have the first
     22interface of the first input will be 0, the second interface of the first input
     23will be 1, the first interface of the second input will be 2, and the second
     24interface of the second input will be 3.
     25
     26Beware that erf only supports 4 interfaces, and pcap only supports 2.
     27Limitations apply based on the input trace format (not the output trace format)
    2028
    2129.TP
Note: See TracChangeset for help on using the changeset viewer.