Commit | Line | Data |
---|---|---|
e24c98a2 MR |
1 | .\" Copyright (c) 1988, 1989, 1991 Carnegie Mellon University |
2 | .\" | |
3 | .\" $Header: /b/source/CVS/othersrc/bootpd/bootpd.8,v 1.2 1993/09/11 13:21:20 andrew Exp $ | |
4 | .\" | |
5 | .TH BOOTPD 8 "November 11, 1991" "Carnegie Mellon University" | |
6 | .UC 6 | |
7 | ||
8 | .SH NAME | |
9 | bootpd \- Internet Boot Protocol server | |
10 | .SH SYNOPSIS | |
11 | .B /usr/libexec/bootpd | |
12 | [ | |
13 | .B \-i | |
14 | .B \-s | |
15 | .B \-t | |
16 | timeout | |
17 | .B \-d | |
18 | level | |
19 | ] | |
20 | [ | |
21 | .I configfile | |
22 | [ | |
23 | .I dumpfile | |
24 | ] ] | |
25 | .SH DESCRIPTION | |
26 | .I Bootpd | |
27 | implements an Internet Bootstrap Protocol server as defined in RFC951, | |
28 | RFC1048, and RFC1084. It is normally run by | |
29 | .I /usr/sbin/inetd | |
30 | by including the following line in the file | |
31 | .IR /etc/inetd.conf : | |
32 | .PP | |
33 | .br | |
34 | bootps dgram udp wait root /usr/libexec/bootpd bootpd | |
35 | .PP | |
36 | This mode of operation is referred to as "inetd mode" and causes | |
37 | .I bootpd | |
38 | to be started only when a boot request arrives. If | |
39 | .I bootpd | |
40 | does not receive another boot request within fifteen minutes of the last one | |
41 | it received, it will exit to conserve system resources. The | |
42 | .B \-t | |
43 | switch may be used to specify a different timeout value in minutes (e.g. | |
44 | -t 20). A timeout value of zero means forever. | |
45 | .PP | |
46 | It is also possible to run | |
47 | .I bootpd | |
48 | in "standalone mode" (without | |
49 | .IR inetd ) | |
50 | by simply invoking it from a shell like any other regular command. | |
51 | Standalone mode is probably the desired mode of operation for large network | |
52 | installations with many BOOTP clients. (The greater the number of clients | |
53 | listed in the configuration database, | |
54 | .IR /etc/bootptab , | |
55 | the longer it takes | |
56 | .I bootpd | |
57 | to start up. To ensure quick response to clients in a large network, | |
58 | it is better to start | |
59 | .I bootpd | |
60 | once during the server machine's bootup sequence. This can be done by invoking | |
61 | .I bootpd | |
62 | from within | |
63 | .IR /etc/rc.local , | |
64 | for example.) | |
65 | . | |
66 | In standalone mode, the | |
67 | .B \-t | |
68 | switch has no effect since | |
69 | .I bootpd | |
70 | will never exit. | |
71 | .PP | |
72 | The server automatically detects whether it was invoked from inetd or from a | |
73 | shell and automatically selects the appropriate mode. For compatibility with | |
74 | older versions of | |
75 | .IR bootpd , | |
76 | the | |
77 | .B \-s | |
78 | switch may be used to force standalone operation. Similarly, the | |
79 | .B \-i | |
80 | switch may be used to force the inetd mode of operation. Normally, though, | |
81 | it should be unnecessary to use these switches. | |
82 | .PP | |
83 | The | |
84 | .B \-d | |
85 | switch takes a numeric parameter which sets the level of debugging output. | |
86 | For example, -d4 or -d 4 will set the debugging level to 4. | |
87 | For compatibility with older versions of | |
88 | .IR bootpd , | |
89 | omitting the numeric parameter (i.e. just -d) will | |
90 | simply increment the debug level by one. | |
91 | .PP | |
92 | Upon startup, | |
93 | .I bootpd | |
94 | first reads its configuration file, | |
95 | .IR /etc/bootptab , | |
96 | and then begins listening for BOOTREQUEST packets. | |
97 | .PP | |
98 | .I Bootpd | |
99 | looks in | |
100 | .I /etc/services | |
101 | to find the UDP port numbers it should use. Two entries are extracted: | |
102 | .BR bootps , | |
103 | the bootp server listening port, and | |
104 | .BR bootpc , | |
105 | the destination port used to reply to clients. If the port numbers cannot | |
106 | be determined this way, | |
107 | .I bootpd | |
108 | defaults to using 67 for the server and 68 for the client. | |
109 | .PP | |
110 | .I Bootpd | |
111 | completely reloads its configuration file when it receives a hangup signal, | |
112 | SIGHUP, or when it receives a BOOTREQUEST packet and detects that the file | |
113 | has been updated. If | |
114 | .I bootpd | |
115 | is compiled with the -DDEBUG option, receipt of a SIGUSR1 signal causes it | |
116 | to dump its memory-resident database to | |
117 | the file | |
118 | .I /etc/bootpd.dump | |
119 | or the command-line-specified dumpfile. | |
120 | ||
121 | .SH FILES | |
122 | /etc/bootptab | |
123 | .br | |
124 | /etc/bootpd.dump | |
125 | .br | |
126 | /etc/services | |
127 | ||
128 | .SH BUGS | |
129 | Individual host entries must not exceed 1024 characters. | |
130 | ||
131 | .SH HISTORY | |
132 | .TP | |
133 | 22-Jan-86 Bill Croft at Stanford University | |
134 | .br | |
135 | Created. | |
136 | ||
137 | .TP | |
138 | 30-Jul-86 David Kovar at Carnegie Mellon University | |
139 | .br | |
140 | Modified to CMU specifications. | |
141 | ||
142 | .TP | |
143 | 24-Jul-87 Drew D. Perkins at Carnegie Mellon University | |
144 | .br | |
145 | Modified to use syslog. Added debugging dumps. Other bug fixes. | |
146 | ||
147 | .TP | |
148 | 17-Jul-88 Walter L. Wimer at Carnegie Mellon University | |
149 | .br | |
150 | Added vendor information to conform to RFC1048. | |
151 | Adopted termcap-like file format to allow variable data. | |
152 | ||
153 | .TP | |
154 | 11-Nov-91 Walter L. Wimer at Carnegie Mellon University | |
155 | .br | |
156 | Added TFTP directory- and server-specification features. Added automatic | |
157 | detection of inetd/standalone mode, making -s switch no longer necessary. | |
158 | Other minor improvements and bug fixes. | |
159 | ||
160 | .SH "SEE ALSO" | |
161 | .br | |
162 | bootptab(5), inetd(8), tftpd(8), | |
163 | .br | |
164 | DARPA Internet Request For Comments RFC951, RFC1048, RFC1084, Assigned Numbers |