1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
|
From: Rafael Cunha de Almeida <rafael@kontesti.me>
Forwarded: Yes
Last-Update: 2010-12-01
Description: Fix spelling in documentation
There are a few spelling errors in manpages and Tips_and_Tricks.txt
file. This patch takes cares of those. Also, lintian reports the use of
an hyphen instead of a minus in a few points of the manpage, this patch
fixes that as well.
diff --git a/doc/tcpstat.1 b/doc/tcpstat.1
index 10cfcce..be60b1a 100644
--- a/doc/tcpstat.1
+++ b/doc/tcpstat.1
@@ -64,7 +64,7 @@ interface, and to show current statistics on it.
.Pp
.Ar interval
is the sample interval, in seconds, in which the statistics are based upon
-and when in default mode, how often the display is updated. If -1 is
+and when in default mode, how often the display is updated. If \-1 is
given, then the interval is taken to be the entire length of the sample.
Default is 5 seconds.
.Pp
@@ -154,7 +154,7 @@ files) and "snoop" format files.
.Ar filename
is usually a file created by the
.Xr tcpdump 1
-command using the "-w" option.
+command using the "\-w" option.
.It Fl s Ar seconds
When monitoring an interface,
.Nm
@@ -261,7 +261,7 @@ will print any remaining statistics, and then exit.
Upon receiving a SIGUSR1 when printing intervals,
.Nm
will print the current statistics immediately. This can be useful
-when using an interval length of "-1" to print statistics on demand.
+when using an interval length of "\-1" to print statistics on demand.
.Sh FILES
.Bl -tag -width /dev/bpfXXX -compact
.It Pa /dev/bpf Ns Sy n
@@ -307,24 +307,24 @@ the bandwidth reported will not reflect this when
is sufficiently large. This results in an "averaging" effect, which may or
may not be desired. On the other hand, if
.Ar interval
-is too small (say < 0.01), this results in unrealisticaly large
+is too small (say < 0.01), this results in unrealistically large
bandwidths for very short amounts of time.
.Pp
The reason for the latter is that most network interfaces do not hand over
packets bit by bit, but rather packet by packet. Thus, each packet is
-reported as being tranfered "instantaneously", resulting in "infinite" (or
+reported as being transferred "instantaneously", resulting in "infinite" (or
rather indeterminable) bandwidth. Thus, when counting single bits on the
wire, there really is no such thing as "bandwidth" because they aren't
really moving from the network stack's point of view (cf. Zeno's Paradox.)
.Pp
-A possible solution is to internaly spline the packet sizes together and
+A possible solution is to internally spline the packet sizes together and
report the bandwidth as the scalar integral over the given interval, but
-this has yet to be implimented, and to be honest, would be the proverbial
-cruise missle to destroy an ant hill.
+this has yet to be implemented, and to be honest, would be the proverbial
+cruise missile to destroy an ant hill.
.Pp
That being said (whew!), a "good value" for
.Ar interval
-is usualy somewhere between 0.5 and 2.
+is usually somewhere between 0.5 and 2.
.Ss Difference between normal and 'dumb' bandwidth modes.
In normal bandwidth mode, when an interval exceeds the given bandwidth,
the extra bytes are "moved" into the next interval. This has the effect
@@ -337,7 +337,7 @@ is simply counted. Nothin' else.
.Nm
was first written in Winter 1998 using
.Fx 3.0 ,
-and then finaly retrofited for Linux in Spring 2000.
+and then finally retrofitted for Linux in Spring 2000.
.Sh AUTHORS
.An Paul Herman Aq pherman@frenchfries.net
.br
@@ -345,7 +345,7 @@ Cologne, Germany.
.Pp
Please send all bug reports to this address.
.Sh BUGS
-Due to a bug in libpcap, tcpstat will hang indefinately under Linux
+Due to a bug in libpcap, tcpstat will hang indefinitely under Linux
when no packets arrive. This is because the timeout in pcap_open_live()
is ignored under Linux when the interface is idle, which causes pcap_dispatch()
to never return.
diff --git a/doc/tcpprof.1 b/doc/tcpprof.1
index 52a455f..c6eebbb 100644
--- a/doc/tcpprof.1
+++ b/doc/tcpprof.1
@@ -113,14 +113,14 @@ is the default) when doing live captures.
.It Fl r Ar filename
Read all data from
.Ar filename ,
-which may be a regular file, a named pipe or "-" to read it's data from
+which may be a regular file, a named pipe or "\-" to read it's data from
standard input. Acceptable file formats include pcap
.Xr (tcpdump 1
files) and "snoop" format files.
.Ar filename
is usually a file created by the
.Xr tcpdump 1
-command using the "-w" option.
+command using the "\-w" option.
.It Fl S Ar letters
Tells
.Nm
@@ -183,7 +183,7 @@ generated file "file.dump".
.Sh HISTORY
.Nm
was first written along side tcpstat in Winter 1998 using FreeBSD 3.0,
-and then finaly retrofited for Linux in Spring 2000. It became installed
+and then finally retrofitted for Linux in Spring 2000. It became installed
along with tcpstat since version 1.5.
.Sh AUTHORS
.An Paul Herman Aq pherman@frenchfries.net
diff --git a/doc/Tips_and_Tricks.txt b/doc/Tips_and_Tricks.txt
index fcb4dc2..73169e9 100644
--- a/doc/Tips_and_Tricks.txt
+++ b/doc/Tips_and_Tricks.txt
@@ -141,7 +141,7 @@ heck did that -o option do? Starting from left to right:
\t - follow timestamp with a tab character to separate data
%T - print the number of TCP packets for this interval
\n - ...followed by a newline
- %3 - tell tcpstat that the following data is outputed to filedesc 3
+ %3 - tell tcpstat that the following data is outputted to filedesc 3
%s\t - once again, a timestamp followed by tab (like above) on filedesc 3
%U - print on filedesc 3 the number of UDP packets for this interval.
\n - newline on filedesc 3
|
