Index Index for
Section 8
Index Alphabetical
listing for B
Bottom of page Bottom of
page		 

bootpd(8)


NAME

  bootpd - Internet Boot Protocol (BOOTP) server


SYNOPSIS

  /usr/opt/obsolete/usr/sbin/bootpd [-c chdir-path] [-ttimeout] [-d debug-
  level] [configfile [dumpfile]]


OPTIONS

  -c chdir-path
      Sets the current directory used by a bootpd process while checking the
      existence and size of client boot files.	This is useful when client
      boot files are specified as relative pathnames and the bootpd process
      needs to use the same current directory as the TFTP server (typically
      /tftpboot).

  -d debug-level
      Sets the debug-level variable that controls the number of debugging
      messages generated.  For example, -d 4 sets the debugging level to 4.
      Valid entries are 1 to 4, where 1 specifies lower level of messages and
      4 the highest.

  -ttimeout
      Specifies the timeout value (in minutes) that a bootpd process waits
      for a BOOTP packet before exiting.  If no packets are received for
      timeout minutes, the program exits.  A timeout value of zero means that
      a bootpd process will wait forever.  When the bootpd daemon is not
      started using the inetd daemon, this option is forced to zero.


DESCRIPTION

  The bootpd daemon implements an Internet Boot Protocol server as defined in
  RFC 951, RFC 1532, and RFC 1533. In order to use the bootpd daemon, you
  must install the Obsolete Commands and Utilities subset (OSFOBSOLETExxx).
  It can be started by the /usr/sbin/inetd daemon by including the following
  line in the /etc/inetd.conf file:

       bootps dgram udp wait root /usr/sbin/bootpd bootpd

  This causes bootpd to be started only when a boot request arrives.  If
  bootpd does not receive another boot request within fifteen minutes of the
  last one it received, it exits to conserve system resources.	The -t option
  can be used to specify a different timeout value in minutes (for example,
  -t20).  A timeout value of zero means forever.

  To run the bootpd daemon, you must also run the tftpd daemon.

  Upon startup, bootpd first reads its configuration file, /etc/bootptab, and
  then begins listening for BOOTREQUEST packets.  See bootptab(4) for a
  description of the configuration file. The bootpd daemon looks in
  /etc/services to find the port numbers it should use.	 Two entries are
  extracted:

  bootps
      The bootp server listening port

  bootpc
      The destination port used to reply to clients

  If the port numbers cannot be determined this way, they are assumed to be
  67 for the server and 68 for the client.

  The bootpd daemon rereads its configuration file when it receives a hangup
  signal, SIGHUP, or when it receives a bootp request packet and detects that
  the file has been updated.  Hosts can be added, deleted, or modified when
  the configuration file is reread.  If bootpd is compiled with the -DDEBUG
  option, receipt of a SIGUSR1 signal causes it to dump its memory-resident
  database to the /usr/adm/bootpd.dump file or dumpfile specified in the
  command line.


RESTRICTIONS

  Individual host entries must not exceed 1024 characters.

  You cannot run bootpd and joind on the same system at the same time.


FILES

  /etc/bootptab
      Internet Boot Protocol server.

  /usr/adm/bootpd.dump
      The bootpd daemon dump file.

  /etc/services
      Defines the sockets and protocols used for Internet services.


SEE ALSO

  Commands: bootpgw(8), bprelay(8), inetd(8), joind(8), tftpd(8)

  Files: bootptab(4)

  DARPA Internet Request For Comments:

  Bootstrap Protocol (RFC 951)

  Clarifications and Extensions for the Bootpstrap Protocol (RFC 1532)

  DHCP Options and BOOTP Vendor Extensions (RFC 1533)

Index Index for
Section 8
Index Alphabetical
listing for B
Top of page Top of
page