Package: ntop Version: 3:3.2-10.1 Severity: minor Tags: patch
Found some typos in '/usr/share/man/man8/ntop.8.gz', see attached '.diff'. Hope this helps... -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Shell: /bin/sh linked to /bin/dash Versions of packages ntop depends on: ii adduser 3.105 add and remove users and groups ii debconf [debconf-2.0] 1.5.19 Debian configuration management sy ii libc6 2.7-8 GNU C Library: Shared libraries ii libfreetype6 2.3.5-1+b1 FreeType 2 font engine, shared lib ii libgd2-xpm 2.0.36~rc1~dfsg-1 GD Graphics Library version 2 ii libgdbm3 1.8.3-3 GNU dbm database routines (runtime ii libjpeg62 6b-14 The Independent JPEG Group's JPEG ii libpcap0.7 0.7.2-9 System interface for user-level pa ii libpng12-0 1.2.15~beta5-3 PNG library - runtime ii libssl0.9.8 0.9.8g-7 SSL shared libraries ii zlib1g 1:1.2.3.3.dfsg-11 compression library - runtime ntop recommends no packages. -- debconf information excluded
--- 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:
