7ebed4a
diff -up dhcp-4.0.0/server/dhcpd.conf.5.manpages dhcp-4.0.0/server/dhcpd.conf.5
7ebed4a
--- dhcp-4.0.0/server/dhcpd.conf.5.manpages	2007-11-20 08:34:37.000000000 -1000
7ebed4a
+++ dhcp-4.0.0/server/dhcpd.conf.5	2008-01-02 11:26:38.000000000 -1000
7ebed4a
@@ -513,6 +513,9 @@ pool {
7ebed4a
 };
7ebed4a
 .fi
7ebed4a
 .PP
7ebed4a
+Dynamic BOOTP leases are not compatible with failover, and, as such,
7ebed4a
+you need to disallow BOOTP in pools that you are using failover for.
7ebed4a
+.PP
7ebed4a
 The  server currently  does very  little  sanity checking,  so if  you
7ebed4a
 configure it wrong, it will just  fail in odd ways.  I would recommend
7ebed4a
 therefore that you either do  failover or don't do failover, but don't
7ebed4a
@@ -527,9 +530,9 @@ primary server might look like this:
7ebed4a
 failover peer "foo" {
7ebed4a
   primary;
7ebed4a
   address anthrax.rc.vix.com;
7ebed4a
-  port 519;
7ebed4a
+  port 647;
7ebed4a
   peer address trantor.rc.vix.com;
7ebed4a
-  peer port 520;
7ebed4a
+  peer port 847;
7ebed4a
   max-response-delay 60;
7ebed4a
   max-unacked-updates 10;
7ebed4a
   mclt 3600;
7ebed4a
@@ -588,9 +591,7 @@ statement
7ebed4a
 .B port \fIport-number\fR\fB;\fR
7ebed4a
 .PP
7ebed4a
 The \fBport\fR statement declares the TCP port on which the server
7ebed4a
-should listen for connections from its failover peer.   This statement
7ebed4a
-may not currently be omitted, because the failover protocol does not
7ebed4a
-yet have a reserved TCP port number.
7ebed4a
+should listen for connections from its failover peer.
7ebed4a
 .RE
7ebed4a
 .PP
7ebed4a
 The 
7ebed4a
@@ -602,10 +603,8 @@ statement
7ebed4a
 .PP
7ebed4a
 The \fBpeer port\fR statement declares the TCP port to which the
7ebed4a
 server should connect to reach its failover peer for failover
7ebed4a
-messages.   This statement may not be omitted because the failover
7ebed4a
-protocol does not yet have a reserved TCP port number.   The port
7ebed4a
-number declared in the \fBpeer port\fR statement may be the same as
7ebed4a
-the port number declared in the \fBport\fR statement.
7ebed4a
+messages.  The port number declared in the \fBpeer port\fR statement
7ebed4a
+may be the same as the port number declared in the \fBport\fR statement.
7ebed4a
 .RE
7ebed4a
 .PP
7ebed4a
 The
7ebed4a
@@ -1272,7 +1271,7 @@ the zone containing PTR records - for IS
7ebed4a
 .PP
7ebed4a
 .nf
7ebed4a
 key DHCP_UPDATER {
7ebed4a
-  algorithm HMAC-MD5.SIG-ALG.REG.INT;
7ebed4a
+  algorithm hmac-md5;
7ebed4a
   secret pRP5FapFoJ95JEL06sv4PQ==;
7ebed4a
 };
7ebed4a
 
7ebed4a
@@ -1295,7 +1294,7 @@ dhcpd.conf file:
7ebed4a
 .PP
7ebed4a
 .nf
7ebed4a
 key DHCP_UPDATER {
7ebed4a
-  algorithm HMAC-MD5.SIG-ALG.REG.INT;
7ebed4a
+  algorithm hmac-md5;
7ebed4a
   secret pRP5FapFoJ95JEL06sv4PQ==;
7ebed4a
 };
7ebed4a
 
7ebed4a
@@ -2433,7 +2432,8 @@ statement
7ebed4a
 The \fInext-server\fR statement is used to specify the host address of
7ebed4a
 the server from which the initial boot file (specified in the
7ebed4a
 \fIfilename\fR statement) is to be loaded.   \fIServer-name\fR should
7ebed4a
-be a numeric IP address or a domain name.
7ebed4a
+be a numeric IP address or a domain name.  If no \fInext-server\fR statement
7ebed4a
+applies to a given client, the address 0.0.0.0 is used.
7ebed4a
 .RE
7ebed4a
 .PP
7ebed4a
 The
7ebed4a
diff -up dhcp-4.0.0/common/dhcp-options.5.manpages dhcp-4.0.0/common/dhcp-options.5
7ebed4a
--- dhcp-4.0.0/common/dhcp-options.5.manpages	2007-09-17 07:52:01.000000000 -1000
7ebed4a
+++ dhcp-4.0.0/common/dhcp-options.5	2008-01-02 11:26:38.000000000 -1000
7ebed4a
@@ -896,6 +896,21 @@ classless IP routing - it does not inclu
7ebed4a
 classless IP routing is now the most widely deployed routing standard,
7ebed4a
 this option is virtually useless, and is not implemented by any of the
7ebed4a
 popular DHCP clients, for example the Microsoft DHCP client.
7ebed4a
+.PP
7ebed4a
+NOTE to @PRODUCTNAME@ dhclient users:
7ebed4a
+.br
7ebed4a
+dhclient-script interprets trailing 0 octets of the target as indicating
7ebed4a
+the subnet class of the route, so for the following static-routes value:
7ebed4a
+.br
7ebed4a
+        option static-routes 172.0.0.0 172.16.2.254,
7ebed4a
+.br
7ebed4a
+                             192.168.0.0 192.168.2.254;
7ebed4a
+.br
7ebed4a
+dhclient-script will create routes:
7ebed4a
+.br
7ebed4a
+        172/8 via 172.16.2.254 dev $interface
7ebed4a
+.br
7ebed4a
+        192.168/16 via 192.168.2.254 dev $interface
7ebed4a
 .RE
7ebed4a
 .PP
7ebed4a
 .nf
7ebed4a
diff -up dhcp-4.0.0/client/dhclient-script.8.manpages dhcp-4.0.0/client/dhclient-script.8
7ebed4a
--- dhcp-4.0.0/client/dhclient-script.8.manpages	2006-02-24 13:16:27.000000000 -1000
7ebed4a
+++ dhcp-4.0.0/client/dhclient-script.8	2008-01-02 11:26:38.000000000 -1000
7ebed4a
@@ -47,7 +47,7 @@ customizations are needed, they should b
7ebed4a
 exit hooks provided (see HOOKS for details).   These hooks will allow the
7ebed4a
 user to override the default behaviour of the client in creating a
7ebed4a
 .B /etc/resolv.conf
7ebed4a
-file.
7ebed4a
+file, and to handle DHCP options not handled by default.
7ebed4a
 .PP
7ebed4a
 No standard client script exists for some operating systems, even though
7ebed4a
 the actual client may work, so a pioneering user may well need to create
7ebed4a
@@ -91,6 +91,26 @@ present.   The
7ebed4a
 .B ETCDIR/dhclient-exit-hooks
7ebed4a
 script can modify the valid of exit_status to change the exit status
7ebed4a
 of dhclient-script.
7ebed4a
+.PP
7ebed4a
+Immediately after dhclient brings an interface UP with a new IP address,
7ebed4a
+subnet mask, and routes, in the REBOOT/BOUND states, it will check for the
7ebed4a
+existence of an executable
7ebed4a
+.B ETCDIR/dhclient-up-hooks
7ebed4a
+script, and source it if found. This script can handle DHCP options in
7ebed4a
+the environment that are not handled by default. A per-interface.
7ebed4a
+.B ETCDIR/dhclient-${IF}-up-hooks
7ebed4a
+script will override the generic script and be sourced when interface
7ebed4a
+$IF has been brought up.
7ebed4a
+.PP
7ebed4a
+Immediately before dhclient brings an interface DOWN, removing its IP
7ebed4a
+address, subnet mask, and routes, in the STOP/RELEASE  states, it will
7ebed4a
+check for the existence of an executable
7ebed4a
+.B ETCDIR/dhclient-down-hooks
7ebed4a
+script, and source it if found. This script can handle DHCP options in
7ebed4a
+the environment that are not handled by default. A per-interface
7ebed4a
+.B ETCDIR/dhclient-${IF}-down-hooks
7ebed4a
+script will override the generic script and be sourced when interface
7ebed4a
+$IF is about to be brought down.
7ebed4a
 .SH OPERATION
7ebed4a
 When dhclient needs to invoke the client configuration script, it
7ebed4a
 defines a set of variables in the environment, and then invokes
7ebed4a
diff -up dhcp-4.0.0/client/dhclient.conf.5.manpages dhcp-4.0.0/client/dhclient.conf.5
7ebed4a
--- dhcp-4.0.0/client/dhclient.conf.5.manpages	2007-08-23 06:06:08.000000000 -1000
7ebed4a
+++ dhcp-4.0.0/client/dhclient.conf.5	2008-01-02 11:26:38.000000000 -1000
7ebed4a
@@ -186,9 +186,9 @@ responding to the client send the client
7ebed4a
 options.   Only the option names should be specified in the request
7ebed4a
 statement - not option parameters.   By default, the DHCP server
7ebed4a
 requests the subnet-mask, broadcast-address, time-offset, routers,
7ebed4a
-domain-name, domain-name-servers and host-name options.  Note that if
7ebed4a
-you enter a 'request' statement, you over-ride this default and these
7ebed4a
-options will not be requested.
7ebed4a
+domain-name, domain-name-servers host-name, nis-domain, nis-servers,
7ebed4a
+and ntp-servers options.  Note that if you enter a 'request' statement,
7ebed4a
+you over-ride this default and these options will not be requested.
7ebed4a
 .PP
7ebed4a
 In some cases, it may be desirable to send no parameter request list
7ebed4a
 at all.   To do this, simply write the request statement but specify
7ebed4a
@@ -626,6 +626,18 @@ database and will record the media type 
7ebed4a
 Whenever the client tries to renew the lease, it will use that same
7ebed4a
 media type.   The lease must expire before the client will go back to
7ebed4a
 cycling through media types.
7ebed4a
+.PP
7ebed4a
+ \fBbootp-broadcast-always;\fR
7ebed4a
+.PP
7ebed4a
+The
7ebed4a
+.B bootp-broadcast-always
7ebed4a
+statement instructs dhclient to always set the bootp broadcast flag in
7ebed4a
+request packets, so that servers will always broadcast replies.
7ebed4a
+This is equivalent to supplying the dhclient -B argument, and has
7ebed4a
+the same effect as specifying 'always-broadcast' in the server's dhcpd.conf.
7ebed4a
+This option is provided as an extension to enable dhclient to work
7ebed4a
+on IBM s390 Linux guests.
7ebed4a
+.PP
7ebed4a
 .SH SAMPLE
7ebed4a
 The following configuration file is used on a laptop running NetBSD
7ebed4a
 1.3.   The laptop has an IP alias of 192.5.5.213, and has one
7ebed4a
diff -up dhcp-4.0.0/client/dhclient.8.manpages dhcp-4.0.0/client/dhclient.8
7ebed4a
--- dhcp-4.0.0/client/dhclient.8.manpages	2007-10-04 07:13:25.000000000 -1000
7ebed4a
+++ dhcp-4.0.0/client/dhclient.8	2008-01-02 11:26:38.000000000 -1000
7ebed4a
@@ -91,6 +91,33 @@ relay
7ebed4a
 .B -w
7ebed4a
 ]
7ebed4a
 [
7ebed4a
+.B -B
7ebed4a
+]
7ebed4a
+[
7ebed4a
+.B -I
7ebed4a
+.I dhcp-client-identifier
7ebed4a
+]
7ebed4a
+[
7ebed4a
+.B -H
7ebed4a
+.I host-name
7ebed4a
+]
7ebed4a
+[
7ebed4a
+.B -F
7ebed4a
+.I fqdn.fqdn
7ebed4a
+]
7ebed4a
+[
7ebed4a
+.B -V
7ebed4a
+.I vendor-class-identifier
7ebed4a
+]
7ebed4a
+[
7ebed4a
+.B -R
7ebed4a
+.I request-option-list
7ebed4a
+]
7ebed4a
+[
7ebed4a
+.B -T
7ebed4a
+.I timeout
7ebed4a
+]
7ebed4a
+[
7ebed4a
 .B -v
7ebed4a
 ]
7ebed4a
 [
7ebed4a
@@ -118,16 +145,6 @@ important details about the network to w
7ebed4a
 the location of a default router, the location of a name server, and
7ebed4a
 so on.
7ebed4a
 .PP
7ebed4a
-If given the -4 command line argument (default), dhclient will use the
7ebed4a
-DHCPv4 protocol to obtain an IPv4 address and configuration parameters.
7ebed4a
-.PP
7ebed4a
-If given the -6 command line argument, dhclient will use the DHCPv6
7ebed4a
-protocol to obtain whatever IPv6 addresses are available along with
7ebed4a
-configuration parameters.  Information-request is not yet supported.
7ebed4a
-.PP
7ebed4a
-If given the --version command line argument, dhclient will print its
7ebed4a
-version number and exit.
7ebed4a
-.PP
7ebed4a
 On startup, dhclient reads the
7ebed4a
 .IR dhclient.conf
7ebed4a
 for configuration instructions.   It then gets a list of all the
7ebed4a
@@ -181,67 +198,183 @@ file.   If interfaces are specified in t
7ebed4a
 only configure interfaces that are either specified in the
7ebed4a
 configuration file or on the command line, and will ignore all other
7ebed4a
 interfaces.
7ebed4a
-.PP
7ebed4a
-If the DHCP client should listen and transmit on a port other than the
7ebed4a
-standard (port 68), the
7ebed4a
-.B -p
7ebed4a
-flag may used.  It should be followed by the udp port number that
7ebed4a
-dhclient should use.  This is mostly useful for debugging purposes.
7ebed4a
-If a different port is specified for the client to listen on and
7ebed4a
-transmit on, the client will also use a different destination port -
7ebed4a
-one greater than the specified destination port.
7ebed4a
-.PP
7ebed4a
-The DHCP client normally transmits any protocol messages it sends
7ebed4a
-before acquiring an IP address to, 255.255.255.255, the IP limited
7ebed4a
-broadcast address.   For debugging purposes, it may be useful to have
7ebed4a
-the server transmit these messages to some other address.   This can
7ebed4a
-be specified with the 
7ebed4a
-.B -s
7ebed4a
-flag, followed by the IP address or domain name of the destination.
7ebed4a
-.PP
7ebed4a
-For testing purposes, the giaddr field of all packets that the client
7ebed4a
-sends can be set using the
7ebed4a
-.B -g
7ebed4a
-flag, followed by the IP address to send.   This is only useful for testing,
7ebed4a
-and should not be expected to work in any consistent or useful way.
7ebed4a
-.PP
7ebed4a
-The DHCP client will normally run in the foreground until it has
7ebed4a
-configured an interface, and then will revert to running in the
7ebed4a
-background.   To run force dhclient to always run as a foreground
7ebed4a
-process, the
7ebed4a
-.B -d
7ebed4a
-flag should be specified.  This is useful when running the client
7ebed4a
-under a debugger, or when running it out of inittab on System V
7ebed4a
-systems.
7ebed4a
-.PP
7ebed4a
-The dhclient daemon creates its own environment when executing the
7ebed4a
-dhclient-script to do the grunt work of interface configuration.
7ebed4a
-To define extra environment variables and their values, use the
7ebed4a
-.B -e
7ebed4a
-flag, followed by the environment variable name and value assignment,
7ebed4a
-just as one would assign a variable in a shell.  Eg:
7ebed4a
-.B -e
7ebed4a
-.I IF_METRIC=1
7ebed4a
-.PP
7ebed4a
-The client normally prints no output during its startup sequence.  It
7ebed4a
-can be made to emit verbose messages displaying the startup sequence events
7ebed4a
-until it has acquired an address by supplying the
7ebed4a
-.B -v
7ebed4a
-command line argument.  In either case, the client logs messages using
7ebed4a
-the
7ebed4a
-.B syslog (3)
7ebed4a
-facility.  A
7ebed4a
-.B -q
7ebed4a
-command line argument is provided for backwards compatibility, but since
7ebed4a
-dhclient is quiet by default, it has no effect.
7ebed4a
-.PP
7ebed4a
-The client normally doesn't release the current lease as it is not
7ebed4a
-required by the DHCP protocol.  Some cable ISPs require their clients
7ebed4a
-to notify the server if they wish to release an assigned IP address.
7ebed4a
+.SH OPTIONS
7ebed4a
+.TP
7ebed4a
+.BI \-4
7ebed4a
+Use the DHCPv4 protocol to obtain an IPv4 address and configuration
7ebed4a
+parameters.
7ebed4a
+
7ebed4a
+.TP
7ebed4a
+.BI \-6
7ebed4a
+Use the DHCPv6 protocol to obtain whatever IPv6 addresses are available
7ebed4a
+along with configuration parameters.  Information-request is not yet
7ebed4a
+supported.
7ebed4a
+
7ebed4a
+.TP
7ebed4a
+.BI \-p\ <port\ number>
7ebed4a
+The UDP port number the DHCP client should listen and transmit on.  If
7ebed4a
+unspecified,
7ebed4a
+.B dhclient
7ebed4a
+uses the default port 68.  This option is mostly useful for debugging
7ebed4a
+purposes.  If a different port is specified for the client to listen and
7ebed4a
+transmit on, the client will also use a different destination port - one
7ebed4a
+greater than the specified destination port.
7ebed4a
+
7ebed4a
+.TP
7ebed4a
+.BI \-d
7ebed4a
+Force
7ebed4a
+.B dhclient
7ebed4a
+to run as a foreground process.  This is useful when running the client
7ebed4a
+under a debugger, or when running it out of inittab on System V systems.
7ebed4a
+
7ebed4a
+.TP
7ebed4a
+.BI \-e\ VAR=value
7ebed4a
+Define additional environment variables for the environment where
7ebed4a
+dhclient-script executes.  You may specify multiple
7ebed4a
+.B \-e
7ebed4a
+options on the command line.
7ebed4a
+
7ebed4a
+.TP
7ebed4a
+.BI \-q
7ebed4a
+Suppress all terminal and log output except error messages.
7ebed4a
+
7ebed4a
+.TP
7ebed4a
+.BI \-1
7ebed4a
+Try one to get a lease.  On failure, exit with code 2.
7ebed4a
+
7ebed4a
+.TP
7ebed4a
+.BI \-r
7ebed4a
+Tell
7ebed4a
+.B dhclient
7ebed4a
+to release the current lease it has from the server.  This is not required
7ebed4a
+by the DHCP protocol, but some ISPs require their clients to notify the
7ebed4a
+server if they wish to release an assigned IP address.
7ebed4a
+
7ebed4a
+.TP
7ebed4a
+.BI \-lf\ <lease-file>
7ebed4a
+Path to the lease database file.  If unspecified, the default
7ebed4a
+.B DBDIR/dhclient.leases
7ebed4a
+is used.
7ebed4a
+
7ebed4a
+.TP
7ebed4a
+.BI \-pf\ <pid-file>
7ebed4a
+Path to the process ID file.  If unspecified, the default
7ebed4a
+.B RUNDIR/dhclient.pid
7ebed4a
+is used.
7ebed4a
+
7ebed4a
+.TP
7ebed4a
+.BI \-cf\ <config-file>
7ebed4a
+Path to the client configuration file.  If unspecified, the default
7ebed4a
+.B ETCDIR/dhclient.conf
7ebed4a
+is used.
7ebed4a
+
7ebed4a
+.TP
7ebed4a
+.BI \-sf\ <script-file>
7ebed4a
+Path to the network configuration script invoked by
7ebed4a
+.B dhclient
7ebed4a
+when it gets a lease.  If unspecified, the default
7ebed4a
+.B CLIENTBINDIR/dhclient-script
7ebed4a
+is used.
7ebed4a
+
7ebed4a
+.TP
7ebed4a
+.BI \-s\ <server>
7ebed4a
+Specifiy the server IP address or fully qualified domain name to transmit
7ebed4a
+DHCP protocol messages to.  Normally,
7ebed4a
+.B dhclient
7ebed4a
+transmits these messages to 255.255.255.255 (the IP limited broadcast
7ebed4a
+address).  Overriding this is mostly useful for debugging purposes.
7ebed4a
+
7ebed4a
+.TP
7ebed4a
+.BI \-g\ <relay>
7ebed4a
+Only for debugging.  Set the giaddr field of all packets the client
7ebed4a
+sends to the IP address specified.  This should not be expected to work
7ebed4a
+in any consistent or useful way.
7ebed4a
+
7ebed4a
+.TP
7ebed4a
+.BI \-n
7ebed4a
+Do not configure any interfaces.  Most useful combined with the
7ebed4a
+.B -w
7ebed4a
+option.
7ebed4a
+
7ebed4a
+.TP
7ebed4a
+.BI \-nw
7ebed4a
+Become a daemon process immediately (nowait) rather than waiting until an IP
7ebed4a
+address has been acquired.
7ebed4a
+
7ebed4a
+.TP
7ebed4a
+.BI \-w
7ebed4a
+Keep running even if no network interfaces are found.  The
7ebed4a
+.B omshell
7ebed4a
+program can be used to notify the client when a network interface has been
7ebed4a
+added or removed so it can attempt to configure an IP address on that
7ebed4a
+interface.
7ebed4a
+
7ebed4a
+.TP
7ebed4a
+.BI \-B
7ebed4a
+Set the BOOTP broadcast flag in request packets so servers will always
7ebed4a
+broadcast replies.
7ebed4a
+
7ebed4a
+.TP
7ebed4a
+.BI \-I\ <dhcp-client-identifier>
7ebed4a
+Specify the dhcp-client-identifier option to send to the DHCP server.
7ebed4a
+
7ebed4a
+.TP
7ebed4a
+.BI \-H\ <host-name>
7ebed4a
+Specify the host-name option to send to the DHCP server.  The host-name
7ebed4a
+string only contains the client's hostname prefix, to which the server will
7ebed4a
+append the ddns-domainname or domain-name options, if any, to derive the
7ebed4a
+fully qualified domain name of the client.  The
7ebed4a
+.B -H
7ebed4a
+option cannot be used with the
7ebed4a
+.B -F
7ebed4a
+option.
7ebed4a
+
7ebed4a
+.TP
7ebed4a
+.BI \-F\ <fqdn.fqdn>
7ebed4a
+Specify the fqdn.fqdn option to send to the DHCP server.  This option cannot
7ebed4a
+be used with the
7ebed4a
+.B -H
7ebed4a
+option.  The fqdn.fqdn option must specify the complete domain name of the
7ebed4a
+client host, which the server may use for dynamic DNS updates.
7ebed4a
+
7ebed4a
+.TP
7ebed4a
+.BI \-V\ <vendor-class-identifier>
7ebed4a
+Specify the vendor-class-identifier option to send to the DHCP server.
7ebed4a
+
7ebed4a
+.TP
7ebed4a
+.BI \-R\ <option>[,<option>...]
7ebed4a
+Specify the list of options the client is to request from the server.  The
7ebed4a
+option list must be a single string consisting of option names separated
7ebed4a
+by at least one command and optional space characters.  The default option
7ebed4a
+list is:
7ebed4a
+
7ebed4a
+.BR
7ebed4a
+    subnet-mask, broadcast-address, time-offset, routers,
7ebed4a
+.BR
7ebed4a
+    domain-name, domain-name-servers, host-name, nis-domain,
7ebed4a
+.BR
7ebed4a
+    nis-servers, ntp-servers
7ebed4a
+
7ebed4a
 The
7ebed4a
-.B -r
7ebed4a
-flag explicitly releases the current lease, and once the lease has been
7ebed4a
-released, the client exits.
7ebed4a
+.B -R
7ebed4a
+option does not append options to the default request, it overrides the
7ebed4a
+default request list.  Keep this in mind if you want to request an
7ebed4a
+additional option besides the default request list.  You will have to
7ebed4a
+specify all option names for the
7ebed4a
+.B -R
7ebed4a
+parameter.
7ebed4a
+
7ebed4a
+.TP
7ebed4a
+.BI \-T\ <timeout>
7ebed4a
+Specify the time after which
7ebed4a
+.B dhclient
7ebed4a
+will decide that no DHCP servers can be contacted when no responses have been
7ebed4a
+received.
7ebed4a
+
7ebed4a
+.TP
7ebed4a
+.BI \-v
7ebed4a
+Enable verbose log messages.
7ebed4a
+
7ebed4a
 .PP
7ebed4a
 If the client is killed by a signal (for example at shutdown or reboot)
7ebed4a
 it won't execute the
7ebed4a
@@ -253,57 +386,7 @@ or
7ebed4a
 it will execute
7ebed4a
 .B dhclient-script (8)
7ebed4a
 at shutdown with the specific reason for calling the script set.
7ebed4a
-.PP
7ebed4a
-The
7ebed4a
-.B -1
7ebed4a
-flag will cause dhclient to try once to get a lease.  If it fails, dhclient
7ebed4a
-exits with exit code two.
7ebed4a
-.PP
7ebed4a
-The DHCP client normally gets its configuration information from
7ebed4a
-.B ETCDIR/dhclient.conf,
7ebed4a
-its lease database from
7ebed4a
-.B DBDIR/dhclient.leases,
7ebed4a
-stores its process ID in a file called
7ebed4a
-.B RUNDIR/dhclient.pid,
7ebed4a
-and configures the network interface using
7ebed4a
-.B CLIENTBINDIR/dhclient-script
7ebed4a
-To specify different names and/or locations for these files, use the
7ebed4a
-.B -cf,
7ebed4a
-.B -lf,
7ebed4a
-.B -pf
7ebed4a
-and
7ebed4a
-.B -sf
7ebed4a
-flags, respectively, followed by the name of the file.   This can be
7ebed4a
-particularly useful if, for example,
7ebed4a
-.B DBDIR
7ebed4a
-or
7ebed4a
-.B RUNDIR
7ebed4a
-has not yet been mounted when the DHCP client is started.
7ebed4a
-.PP
7ebed4a
-The DHCP client normally exits if it isn't able to identify any
7ebed4a
-network interfaces to configure.   On laptop computers and other
7ebed4a
-computers with hot-swappable I/O buses, it is possible that a
7ebed4a
-broadcast interface may be added after system startup.   The
7ebed4a
-.B -w
7ebed4a
-flag can be used to cause the client not to exit when it doesn't find
7ebed4a
-any such interfaces.   The
7ebed4a
-.B omshell (1)
7ebed4a
-program can then be used to notify the client when a network interface
7ebed4a
-has been added or removed, so that the client can attempt to configure an IP
7ebed4a
-address on that interface.
7ebed4a
-.PP
7ebed4a
-The DHCP client can be directed not to attempt to configure any interfaces
7ebed4a
-using the
7ebed4a
-.B -n
7ebed4a
-flag.   This is most likely to be useful in combination with the
7ebed4a
-.B -w
7ebed4a
-flag.
7ebed4a
-.PP
7ebed4a
-The client can also be instructed to become a daemon immediately, rather
7ebed4a
-than waiting until it has acquired an IP address.   This can be done by
7ebed4a
-supplying the
7ebed4a
-.B -nw
7ebed4a
-flag.
7ebed4a
+
7ebed4a
 .SH CONFIGURATION
7ebed4a
 The syntax of the dhclient.conf(5) file is discussed separately.
7ebed4a
 .SH OMAPI