diff options
author | Tomek Mrugalski <tomek@isc.org> | 2022-01-19 20:14:16 +0100 |
---|---|---|
committer | Tomek Mrugalski <tomek@isc.org> | 2022-01-20 12:04:28 +0100 |
commit | f6b8f48d1665c4487dedbcfa4dca435a0d67ddeb (patch) | |
tree | 19926f31f56890bc8c7f5d3bc5b2e2c16b96794e /client/dhclient.conf.5 | |
parent | 429a56d73c0f9f2edf400fd6313850a3ce4fd809 (diff) | |
download | isc-dhcp-f6b8f48d1665c4487dedbcfa4dca435a0d67ddeb.tar.gz |
[#189] Whitespace fixes in opened files
Diffstat (limited to 'client/dhclient.conf.5')
-rw-r--r-- | client/dhclient.conf.5 | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/client/dhclient.conf.5 b/client/dhclient.conf.5 index 36b97070..d973d11b 100644 --- a/client/dhclient.conf.5 +++ b/client/dhclient.conf.5 @@ -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 @@ -664,7 +664,7 @@ effect that will be addressed in a future release. .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. |