*nix Documentation Project
·  Home
 +   man pages
·  Linux HOWTOs
·  FreeBSD Tips
·  *niX Forums

  man pages->Tru64 Unix man pages -> dhcpparm (8)              



NAME    [Toc]    [Back]

       dhcpparm - Daemon for client configuration

SYNOPSIS    [Toc]    [Back]

       /usr/sbin/dhcpparm [-i interface] tag | symbol | name

OPTIONS    [Toc]    [Back]

       Use  this  option  on hardware that has two or more interfaces
 configurable by the Dynamic Host Configuration  Protocol
  (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)  displayed
       will be those of the configuration received on that interface.

DESCRIPTION    [Toc]    [Back]

       The dhcpparm command displays the value(s) of the  parameter
  requested on the command line as supplied by the DHCP
       protocol.  If the DHCP parameter  implies  more  than  one
       value  (for  example,  a list of gateways), the values are
       displayed separated by newline characters.  The  parameter
       may  be identified either by its numeric value in the DHCP
       protocol, by its two character  symbol,  or  by  its  long
       name.  The dhcpparm command 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  the  -i option specifies a particular interface, the
       daemon verifies  successful  DHCP  configuration  of  that
       interface;  otherwise,  the  client verifies that at least
       one interface is successfully configured, and supplies the
       name  of  that  interface  to  dhcpparm.  Parameter values
       echoed by dhcpparm should not  be  used  without  checking
       exit status. See the EXIT STATUS section below.

RESTRICTIONS    [Toc]    [Back]

       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.

       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.

SYMBOLS    [Toc]    [Back]

       See dhcptags(4) for the list of two  letter  symbol  codes
       and  names  of  all DHCP parameters. See RFC 1533 for more

EXIT STATUS    [Toc]    [Back]

       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 arguments.  A timer was
       set  and  the  interface  had  not  configured  before  it
       expired.   Can  only  be  run  as root.  Some system error
       (should never occur).

SEE ALSO    [Toc]    [Back]

       Commands: dhcpconf(8), joinc(8), showdhc(8), shleases(8)

       Files: client.pcy(4), dhcptags(4)


[ Back ]
 Similar pages
Name OS Title
joinc Tru64 Daemon for DHCP client configuration
cdsadv HP-UX Starts the CDS client daemon
dhcpv6clientd HP-UX DHCPv6 client daemon
bos OpenBSD is the client part of the Basic Overseer Daemon AFS server processes.
dhcpconf Tru64 Controller for DHCP client configuration
tacplus.conf FreeBSD TACACS+ client configuration file
dhclient.conf OpenBSD DHCP client configuration file
ssh_config FreeBSD OpenSSH SSH client configuration files
dhclient.conf Linux DHCP client configuration file
dhclient.conf FreeBSD DHCP client configuration file
Copyright © 2004-2005 DeniX Solutions SRL
newsletter delivery service