Package: isc-dhcp-client
Version: 4.4.1-2.1+b2
Severity: minor
Tags: patch
Dear Maintainer,
<dhclient.conf.5>:32 (macro IR): only 1 argument, but more are expected
troff: backtrace: file '<dhclient.conf.5>':169
troff: <dhclient.conf.5>:169: warning: trailing space
troff: backtrace: file '<dhclient.conf.5>':172
troff: <dhclient.conf.5>:172: warning: trailing space
troff: backtrace: file '<dhclient.conf.5>':353
troff: <dhclient.conf.5>:353: warning: trailing space
troff: backtrace: file '<dhclient.conf.5>':667
troff: <dhclient.conf.5>:667: warning: trailing space
an-end-check:<dhclient.conf.5>: Warning: Different number of .RS and .RE calls,
an-RS-open=1 at end of file
####
The part around ".RS 0.25i" was removed, as it did not correspond
to anything similar, and the reason for it is not understandable.
Patch:
--- dhclient.conf.5 2020-03-23 09:08:55.000000000 +0000
+++ dhclient.conf.5.new 2020-05-19 18:15:21.000000000 +0000
@@ -29,7 +29,7 @@
dhclient.conf - DHCP client configuration file
.SH DESCRIPTION
The dhclient.conf file contains configuration information for
-.IR dhclient,
+.IR dhclient ,
the Internet Systems Consortium DHCP Client.
.PP
The dhclient.conf file is a free-form ASCII text file. It is parsed by
@@ -165,11 +165,11 @@ amount. It defaults to ten seconds.
.PP
\fBinitial-delay \fItime\fR\fB;\fR
.PP
-.I initial-delay
-parameter sets the maximum time client can wait after start before
+.I initial-delay
+parameter sets the maximum time client can wait after start before
commencing first transmission.
According to RFC2131 Section 4.4.1, client should wait a random time between
-startup and the actual first transmission. Previous versions of ISC DHCP
+startup and the actual first transmission. Previous versions of ISC DHCP
client used to wait random time up to 5 seconds, but that was unwanted
due to impact on startup time. As such, new versions have the default
initial delay set to 0. To restore old behavior, please set initial-delay
@@ -350,7 +350,7 @@ statement.
.PP
If for some option the client should always use a locally-configured
value or values rather than whatever is supplied by the server, these
-values can be defined in the
+values can be defined in the
.B supersede
statement.
.PP
@@ -598,12 +598,7 @@ the time value, and helpfully places a l
the same line. The formats are described in detail in this manpage, within
the LEASE DECLARATIONS section.
.PP
-The
-.I lease-id-format
-parameter
-.RS 0.25i
-.PP
-.B lease-id-format \fIformat\fB;\fR
+.B " lease-id-format \fIformat\fB;\fR
.PP
The \fIformat\fR parameter must be either \fBoctal\fR or \fBhex\fR.
This parameter governs the format used to write certain values to lease
@@ -664,7 +659,7 @@ effect that will be addressed in a futur
.PP
\fBpseudo "\fIname\fR" "\fIreal-name\fB" { \fIdeclarations ... \fB }
.PP
-Under some circumstances it can be useful to declare a pseudo-interface
+Under some circumstances it can be useful to declare a pseudo-interface
and have the DHCP client acquire a configuration for that interface.
Each interface that the DHCP client is supporting normally has a DHCP
client state machine running on it to acquire and maintain its lease.
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.4.19-1 (SMP w/2 CPU cores)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1),
LANGUAGE=is_IS.iso88591 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages isc-dhcp-client depends on:
ii debianutils 4.9.1
ii iproute2 5.6.0-1
ii libc6 2.30-8
ii libdns-export1110 1:9.11.18+dfsg-1
ii libisc-export1105 1:9.11.18+dfsg-1
Versions of packages isc-dhcp-client recommends:
ii isc-dhcp-common 4.4.1-2.1+b2
Versions of packages isc-dhcp-client suggests:
pn avahi-autoipd <none>
pn isc-dhcp-client-ddns <none>
pn resolvconf <none>
-- no debconf information
--
Bjarni I. Gislason
