.\" Copyright (c) 1988, 1989, 1991 Carnegie Mellon University
.\" $Header: /b/source/CVS/othersrc/bootpd/bootpd.8,v 1.2 1993/09/11 13:21:20 andrew Exp $
.TH BOOTPD 8 "November 11, 1991" "Carnegie Mellon University"
bootpd \- Internet Boot Protocol server
implements an Internet Bootstrap Protocol server as defined in RFC951,
RFC1048, and RFC1084. It is normally run by
by including the following line in the file
bootps dgram udp wait root /usr/libexec/bootpd bootpd
This mode of operation is referred to as "inetd mode" and causes
to be started only when a boot request arrives. If
does not receive another boot request within fifteen minutes of the last one
it received, it will exit to conserve system resources. The
switch may be used to specify a different timeout value in minutes (e.g.
-t 20). A timeout value of zero means forever.
It is also possible to run
in "standalone mode" (without
by simply invoking it from a shell like any other regular command.
Standalone mode is probably the desired mode of operation for large network
installations with many BOOTP clients. (The greater the number of clients
listed in the configuration database,
to start up. To ensure quick response to clients in a large network,
once during the server machine's bootup sequence. This can be done by invoking
switch has no effect since
The server automatically detects whether it was invoked from inetd or from a
shell and automatically selects the appropriate mode. For compatibility with
switch may be used to force standalone operation. Similarly, the
switch may be used to force the inetd mode of operation. Normally, though,
it should be unnecessary to use these switches.
switch takes a numeric parameter which sets the level of debugging output.
For example, -d4 or -d 4 will set the debugging level to 4.
For compatibility with older versions of
omitting the numeric parameter (i.e. just -d) will
simply increment the debug level by one.
first reads its configuration file,
and then begins listening for BOOTREQUEST packets.
to find the UDP port numbers it should use. Two entries are extracted:
the bootp server listening port, and
the destination port used to reply to clients. If the port numbers cannot
defaults to using 67 for the server and 68 for the client.
completely reloads its configuration file when it receives a hangup signal,
SIGHUP, or when it receives a BOOTREQUEST packet and detects that the file
is compiled with the -DDEBUG option, receipt of a SIGUSR1 signal causes it
to dump its memory-resident database to
or the command-line-specified dumpfile.
Individual host entries must not exceed 1024 characters.
22-Jan-86 Bill Croft at Stanford University
30-Jul-86 David Kovar at Carnegie Mellon University
Modified to CMU specifications.
24-Jul-87 Drew D. Perkins at Carnegie Mellon University
Modified to use syslog. Added debugging dumps. Other bug fixes.
17-Jul-88 Walter L. Wimer at Carnegie Mellon University
Added vendor information to conform to RFC1048.
Adopted termcap-like file format to allow variable data.
11-Nov-91 Walter L. Wimer at Carnegie Mellon University
Added TFTP directory- and server-specification features. Added automatic
detection of inetd/standalone mode, making -s switch no longer necessary.
Other minor improvements and bug fixes.
bootptab(5), inetd(8), tftpd(8),
DARPA Internet Request For Comments RFC951, RFC1048, RFC1084, Assigned Numbers