*** UNIX MANUAL PAGE BROWSER ***

dhcpparm(8) System Manager's Manual dhcpparm(8) NAME dhcpparm - daemon for client configuration SYNOPSIS /usr/sbin/dhcpparm [-i interface] tag | symbol | name FLAGS Use this option on hardware that has two or more interfaces config- urable by DHCP, and for a parameter that is interface specific. When no interface is specified, the client daemon returns the name of the first interface it finds on which DHCP has successfully completed: the value(s) printed will then be those of the configuration received on that interface. DESCRIPTION The dhcpparm command prints the value(s) of the parameter requested on the command line as supplied by the DHCP protocol. If the DHCP parame- ter implies more than one value (for example, a list of gateways), the values are printed separated by newline characters. The parameter may be identified either by its numeric value in the DHCP protocol, or by its two character symbol (q.v.), or by its long name. It is intended to be used in command substitutions in the shell scripts invoked by init at system boot. It first contacts the DHCP client daemon (joinc) to verify that DHCP has successfully completed. When a particular inter- face is given with the -i option, the daemon verifies successful DHCP configuration of that specific interface; otherwise, the client veri- fies that at least one interface has successfully configured, and sup- plies the name of that interface back to dhcpparm. Parameter values echoed by dhcpparm should not be used without checking its exit status. See the Diagnostics section below. SYMBOLS See the dhcptags(4) for the list of two letter symbol codes and names of all DHCP parameters. See RFC1533 for more detail. DIAGNOSTICS Exit codes are as follows: Success. DHCP was not successful. The DHCP client daemon may not be running, the interface might have failed to configure, or no satisfactory DHCP responses were received. Bad argu- ments. A timer was set (with -w) and the interface had not configured before it expired. Can only be run as root. Some system error (should never occur). RESTRICTIONS A cluster member should never be a DHCP client. It should always use static addressing. If a cluster is to support a DHCP server, there can only be one DHCP server for all the cluster members using a common database with failover. DHCP client is not supported on dataless clients. RELATED INFORMATION Commands: dhcpconf(8), joinc(8), showdhc(8), shleases(8). Files: client.pcy(4), dhcptags(4). RFC1533 delim off dhcpparm(8)