To successfully start bootpd,
you must have a current and correct configuration file for it. The
default file is /etc/bootptab
but you may use an alternate configuration file by specifying its
POSIX file name on the command line. Without this configuration
file, bootpd
will not be able to service BOOTP
requests.
You can run bootpd
under the Internet daemon only. You may not run it as a standalone
server.
Starting bootpd Under inetd |
|
If you are running bootpd
with inetd, make
certain that you have edited the inetd
configuration file as explained earlier in this chapter. There is
no special step required of you to start bootpd:
When the Internet daemon is running, it will automatically invoke
bootpd when it
gets a connection request for that service. To find out how to start
inetd, refer
to Chapter 2 “Internet Daemon”
Command Line Options for bootpd |
|
You can change the way that bootpd
operates by entering the bootpd
command followed by one of the command line options. For example:
:BOOTPD.NET.SYS -d
The options available to you are explained below.
- Option
Purpose
- -t
Changes the timeout value for bootpd.
The BOOTP daemon starts when the
first BOOTP request arrives. If
no other boot request arrives within the default period of 15 minutes,
bootpd ends.
If you specify a timeout of 0 minutes, the server will not die until
you abort JINETD or JINETD
ends in an error state.
- -d
Sets the verbosity level for the logging messages
generated by bootpd.
- configfile
The configuration file bootpd
reads to get configuration information, expressed in HFS syntax.
By default, bootpd
uses /etc/bootptab.