Package: dhcp3-server
Version: 3.0.4-6
Severity: minor
Tags: patch

Found some typos in '/usr/share/man/man5/dhcpd.conf.5.gz', see attached '.diff'.

Hope this helps...

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.16-2-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)

Versions of packages dhcp3-server depends on:
ii  debconf [debconf-2.0]         1.5.3      Debian configuration management sy
ii  debianutils                   2.17       Miscellaneous utilities specific t
ii  dhcp3-common                  3.0.4-6    Common files used by all the dhcp3
ii  libc6                         2.3.6-19   GNU C Library: Shared libraries

dhcp3-server recommends no packages.

-- debconf-show failed


--- dhcpd.conf.5        2006-06-20 14:16:20.000000000 -0400
+++ /tmp/dhcpd.conf.5   2006-08-14 02:42:33.000000000 -0400
@@ -1502,7 +1502,7 @@
  \fBdeny duplicates;\fR
 .PP
 Host declarations can match client messages based on the DHCP Client
-Identifer option or based on the client's network hardware type and
+Identifier option or based on the client's network hardware type and
 MAC address.   If the MAC address is used, the host declaration will
 match any client with that MAC address - even clients with different
 client identifiers.   This doesn't normally happen, but is possible
@@ -1836,7 +1836,7 @@
 The \fIdynamic-bootp-lease-cutoff\fR statement sets the ending time
 for all leases assigned dynamically to BOOTP clients.  Because BOOTP
 clients do not have any way of renewing leases, and don't know that
-their leases could expire, by default dhcpd assignes infinite leases
+their leases could expire, by default dhcpd assigns infinite leases
 to all BOOTP clients.  However, it may make sense in some situations
 to set a cutoff date for all BOOTP leases - for example, the end of a
 school term, or the time at night when a facility is closed and all
@@ -2210,7 +2210,7 @@
 server generally uses the \fBlocal-port\fR configuration value.  Should the
 DHCP Relay happen to be addressed as 127.0.0.1, however, the DHCP Server
 transmits its response to the \fBremote-port\fR configuration value.  This
-is generally only useful for testing purposes, and this configuratoin value
+is generally only useful for testing purposes, and this configuration value
 should generally not be used.
 .RE
 .PP


Reply via email to