Changes between Version 5 and Version 6 of TraceReport


Ignore:
Timestamp:
07/28/10 13:39:55 (10 years ago)
Author:
salcock
Comment:

Update tracereport page

Legend:

Unmodified
Added
Removed
Modified
  • TraceReport

    v5 v6  
    22
    33=== Usage ===
    4 {{{tracereport [ -f bpf | --filter=bpf ] [ -e | --error ] [ -F | --flow ] [ -P | --protocol ] [ -p | --port ] [ -T | --tos ] }}}
    5 {{{            [ -t | --ttl ] [ -O | --tcpoptions ] [ -o | --synoptions ] [ -n | --nlp ] [ -d | --direction ] [ -C | --ecn ] }}}
    6 {{{            [ -s | --tcpsegment ] inputuri }}}
     4{{{
     5tracereport
     6        [ -f bpf | --filter=bpf ]
     7        [ -e | --error ]
     8        [ -F | --flow ]
     9        [ -P | --protocol ]
     10        [ -p | --port ]
     11        [ -T | --tos ]
     12        [ -t | --ttl ]
     13        [ -O | --tcpoptions ]
     14        [ -o | --synoptions ]
     15        [ -n | --nlp ]
     16        [ -d | --direction ]
     17        [ -C | --ecn ]
     18        [ -s | --tcpsegment ]
     19inputuri
     20}}}
    721
    822=== Options ===
     
    5165
    5266=== Notes ===
    53  * Unlike most of the other libtrace tools, {{{tracereport}}} is still under active development. Many of the existing reports do not yet conform to the new output scheme we have developed and will just write straight to stdout. We are also likely to add more reports in the future.
     67 * Unlike most of the other libtrace tools, {{{tracereport}}} is still under active development. Previous versions of libtrace may write the report output to stdout rather than to a file. We are also likely to add more reports in the future.
    5468 * The version of tracereport that was distributed with the libtrace-3.0.0 release is actually quite different to what is described above - see the tracereport(1) manpage that came with your distribution for more details.