TRACEMERGE(1)
TRACEMERGE(1) β¨
okay bestie, welcome to the TRACEMERGE(1) page from User Commands β it's giving "merge your traces, no cap" π
π NAME π
tracemerge - Merge one (or more) traces together
π¦ SYNOPSIS π¦
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. periodt.
so here's the tea on every single option, bestie β don't skip a crumb:
-i[interfaces_per_input],--set-interface[interfaces_per_input]β set the interface ("direction") for each input to be unique. The optionalinputs_per_interfaceparameter is how many inputs to reserve for each trace, and defaults to1. Thus if you have two traces with two interfaces (in/out), andinterfaces_per_inputis set to2, thentracemergewill have the first interface of the first input will be0, the second interface of the first input will be1, the first interface of the second input will be2, and the second interface of the second input will be3. Beware thaterfonly supports 4 interfaces, andpcaponly 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 from0(no compression) to9(maximum compression). Higher compression levels require more CPU to compress data. Defaults to0.-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 β go read it, it's lowkey iconic πβ¨
π SEE ALSO π
libtrace(3)tracesplit(1)tracesplit_dir(1)tracefilter(1)traceconvert(1)tracereport(1)tracertstats(1)tracestats(1)tracepktdump(1)traceanon(1)tracesummary(1)tracereplay(1)tracediff(1)traceends(1)tracetopends(1)
π¦ AUTHORS π¦
Perry Lorier <perry@cs.waikato.ac.nz> β thank you for your service, king π
this iconic page is from tracemerge (libtrace), dated March 2006. slay, bye bestie πβ¨
π¦ where this page comes from
- debian bookworm: libtrace-tools 3.0.22-0.1
- debian trixie: libtrace-tools 3.0.22-0.2
- ubuntu jammy: libtrace-tools 3.0.21-1ubuntu5
- ubuntu noble: libtrace-tools 3.0.22-0.2build1
- ubuntu questing: libtrace-tools 3.0.22-0.2build1
- ubuntu resolute: libtrace-tools 3.0.22-0.2build2
- ubuntu stonking: libtrace-tools 3.0.22-0.2build2
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms