File: ntop.8.v1.diff

package info (click to toggle)
ntop 3:3.3-11
  • links: PTS
  • area: main
  • in suites: lenny
  • size: 12,772 kB
  • ctags: 7,534
  • sloc: ansic: 71,427; sh: 16,772; awk: 1,504; perl: 792; makefile: 782; php: 123; python: 23; sql: 13; sed: 11
file content (59 lines) | stat: -rw-r--r-- 2,770 bytes parent folder | download
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
--- ntop.8	2007-05-18 13:56:33.000000000 -0400
+++ /tmp/ntop.8	2008-02-19 02:03:28.000000000 -0500
@@ -327,7 +327,7 @@
 'other' packets are found. The file is in tcpdump (pcap) format and is named
 <path>/ntop-other-pkts.<device>.pcap, where <path> is defined by the 
 -O | --output-packet-path parameter.
-This file is useful for understanding these unclassifed packets.
+This file is useful for understanding these unclassified packets.
 
 .It2 -l --pcap-log
 This parameter causes a dump file to be created of the network traffic captured by 
@@ -788,7 +788,7 @@
 merges the data collected from all of the interfaces (NICs) it is monitoring into a
 single set of counters. 
 
-If you have a simple network, say a small LAN with a connection to the internet, 
+If you have a simple network, say a small LAN with a connection to the Internet, 
 merging data is good as it gives you a better picture of the whole network.
 For larger, more complex networks, this may not be desirable.
 You may also have other reasons for wishing to monitor each interface separately,
@@ -912,7 +912,7 @@
 stores extra information about the locks and unlocks of the protective mutexes it uses. Since
 .B ntop
 uses fine-grained locking, this information is updated frequently.  On some OSes, the system
-calls used to collect this informatio (getpid() and gettimeofday()) are expensive.  This option
+calls used to collect this information (getpid() and gettimeofday()) are expensive.  This option
 disables the extra information.  It should have no processing impact on
 .B ntop
  - however should
@@ -978,7 +978,7 @@
 uses the dladdr() function.  The original Solaris routine had a bug, replicated in
 FreeBSD (and possibly other places) where it uses the ARGV[0] value - which might be
 erroneous - instead of the actual file name.  If the 'running from' value looks bogus but
-the 'libaries in' value looks ok, go with the libarary.
+the 'libraries in' value looks OK, go with the library.
 
 .It --no-fc 
 
@@ -1008,8 +1008,8 @@
 This option sets the non-blocking 
 option (assuming it's available in the version of libpcap that is installed).
 
-While this works around the problem (by turing an interupt driven process into 
-a poll), it also MAY signifcantly increases the cpu usage of
+While this works around the problem (by turning an interrupt driven process into 
+a poll), it also MAY significantly increase the CPU usage of
 .B ntop.
 Although it does not actually interfere with other work, seeing
 .B ntop
@@ -1267,7 +1267,7 @@
 which flags are being used.
 
 The libpcap, gdbm, openssl and zlib versions come from the strings returned by the various
-inquiry functions (if they're availabe).
+inquiry functions (if they're available).
 
 Here's a sample log record: