centos-dhcp配置文件参数解析

原文网址:http://www.freebsd.org/cgi/man.cgi?query=dhclient.conf&sektion=5

NAME
     dhclient.conf -- DHCP client configuration	file

DESCRIPTION
     The dhclient.conf file contains configuration information for
     dhclient(8), the Internet Software	Consortium DHCP	Client.

     The dhclient.conf file is a free-form ASCII text file.  It	is parsed by
     the recursive-descent parser built	into dhclient(8).  The file may	con-
     tain extra	tabs and newlines for formatting purposes.  Keywords in	the
     file are case-insensitive.	 Comments may be placed	anywhere within	the
     file (except within quotes).  Comments begin with the `#' character and
     end at the	end of the line.

     The dhclient.conf file can	be used	to configure the behaviour of the
     client in a wide variety of ways: protocol	timing,	information requested
     from the server, information required of the server, defaults to use if
     the server	does not provide certain information, values with which	to
     override information provided by the server, or values to prepend or
     append to information provided by the server.  The	configuration file can
     also be preinitialized with addresses to use on networks that do not have
     DHCP servers.

PROTOCOL TIMING
     The timing	behaviour of the client	need not be configured by the user.
     If	no timing configuration	is provided by the user, a fairly reasonable
     timing behaviour will be used by default -	one which results in fairly
     timely updates without placing an inordinate load on the server.

     The following statements can be used to adjust the	timing behaviour of
     the DHCP client if	required, however:

     timeout time;
	     The timeout statement determines the amount of time that must
	     pass between the time that	the client begins to try to determine
	     its address and the time that it decides that it is not going to
	     be	able to	contact	a server.  By default, this timeout is sixty
	     seconds.  After the timeout has passed, if	there are any static
	     leases defined in the configuration file, or any leases remaining
	     in	the lease database that	have not yet expired, the client will
	     loop through these	leases attempting to validate them, and	if it
	     finds one that appears to be valid, it will use that lease's
	     address.  If there	are no valid static leases or unexpired	leases
	     in	the lease database, the	client will restart the	protocol after
	     the defined retry interval.

     retry time;
	     The retry statement determines the	time that must pass after the
	     client has	determined that	there is no DHCP server	present	before
	     it	tries again to contact a DHCP server.  By default, this	is
	     five minutes.

     select-timeout time;
	     It	is possible (some might	say desirable) for there to be more
	     than one DHCP server serving any given network.  In this case, it
	     is	possible that a	client may be sent more	than one offer in
	     response to its initial lease discovery message.  It may be that
	     one of these offers is preferable to the other (e.g., one offer
	     may have the address the client previously	used, and the other
	     may not).

	     The select-timeout	is the time after the client sends its first
	     lease discovery request at	which it stops waiting for offers from
	     servers, assuming that it has received at least one such offer.
	     If	no offers have been received by	the time the select-timeout
	     has expired, the client will accept the first offer that arrives.

	     By	default, the select-timeout is zero seconds - that is, the
	     client will take the first	offer it sees.

     reboot time;
	     When the client is	restarted, it first tries to reacquire the
	     last address it had.  This	is called the INIT-REBOOT state.  If
	     it	is still attached to the same network it was attached to when
	     it	last ran, this is the quickest way to get