Ethereal-dev: Re: [Ethereal-dev] Could someone with more knowledge than me update/improve the
Hi,
It is not so much the -r option that is misleading, it's the synopsys
which doesn't make clear that the command can work on a range of packets.
I can suggest the following change for that:
Index: editcap.pod
===================================================================
--- editcap.pod (revision 16189)
+++ editcap.pod (working copy)
@@ -16,7 +16,7 @@
S<[ B<-v> ]>
I<infile>
I<outfile>
-S<[ I<record#> ... ]>
+S<[ [-I<record#>] | [I<record#>[-[I<record#>]] ] [...]>
=head1 DESCRIPTION
This changes the synopsys into
SYNOPSYS
editcap [ -E error probability] [ -F file format ] [ -h ] [ -r ]
[ -s snaplen ] [ -t time adjustment ] [ -T encapsulation type ]
[ -v ] infile outfile [ [-record#] | [record#[-[record#]] ] [...]
And even though it is more complicated it covers the ranges question.
Greetz,
Jaap
On Tue, 11 Oct 2005, Ulf Lamping wrote:
> Hi List!
>
> The description of the packet range and the -r option seems to be
> misleading.
>
> As I don't know the current implementation well, could someone have a
> look at it?
[SNIP]
> The information that a range of packets can be specified is buried very
> deeply inside the Description only. Information that an "open end" range
> e.g. "10000-" is also possible is completely missing.
>
> As this is one of the major usages of the tool it should be in a more
> prominent place.
>
> Regards, ULFL
