1 .\" Copyright (c) 1988, 1992 The University of Utah and the Center
2 .\" for Software Science (CSS).
3 .\" Copyright (c) 1992, 1993
4 .\" The Regents of the University of California. All rights reserved.
6 .\" This code is derived from software contributed to Berkeley by
7 .\" the Center for Software Science of the University of Utah Computer
8 .\" Science Department. CSS requests users of this software to return
9 .\" to css-dist@cs.utah.edu any improvements that they make and grant
10 .\" CSS redistribution rights.
12 .\" Redistribution and use in source and binary forms, with or without
13 .\" modification, are permitted provided that the following conditions
15 .\" 1. Redistributions of source code must retain the above copyright
16 .\" notice, this list of conditions and the following disclaimer.
17 .\" 2. Redistributions in binary form must reproduce the above copyright
18 .\" notice, this list of conditions and the following disclaimer in the
19 .\" documentation and/or other materials provided with the distribution.
20 .\" 3. All advertising materials mentioning features or use of this software
21 .\" must display the following acknowledgement:
22 .\" This product includes software developed by the University of
23 .\" California, Berkeley and its contributors.
24 .\" 4. Neither the name of the University nor the names of its contributors
25 .\" may be used to endorse or promote products derived from this software
26 .\" without specific prior written permission.
28 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
29 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
30 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
31 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
32 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
33 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
34 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
35 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
36 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
37 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
40 .\" from: @(#)rbootd.8 8.2 (Berkeley) 12/11/93
43 .\" Utah Hdr: rbootd.man 3.1 92/07/06
44 .\" Author: Jeff Forys, University of Utah CSS
51 .Nd HP remote boot server
60 utility services boot requests from Hewlett-Packard workstations over a
62 All boot files must reside in the boot file directory; further, if a
63 client supplies path information in its boot request, it will be silently
64 stripped away before processing.
67 only responds to requests from machines listed in its configuration file.
69 The options are as follows:
70 .Bl -tag -width indent
72 Respond to boot requests from any machine.
73 The configuration file is ignored if this option is specified.
78 Packets sent and received are displayed to the terminal.
80 Service boot requests on specified interface.
83 searches the system interface list for the lowest numbered, configured
84 ``up'' interface (excluding loopback).
85 Ties are broken by choosing the earliest match.
90 on the command line causes
92 to use a different configuration file from the default.
94 The configuration file is a text file where each line describes a particular
96 A line must start with a machine's Ethernet address followed by an optional
97 list of boot file names.
98 An Ethernet address is specified in hexadecimal with each of its six octets
100 The boot file names come from the boot file directory.
101 The ethernet address and boot file(s) must be separated by white-space
102 and/or comma characters.
103 A pound sign causes the remainder of a line to be ignored.
105 Here is a sample configuration file:
106 .Bl -column 08:00:09:0:66:ad SYSHPBSD,SYSHPUX "# vandy (anything)"
108 .It # ethernet addr boot file(s) comments
110 .It 08:00:09:0:66:ad SYSHPBSD # snake (4.3BSD)
111 .It 08:00:09:0:59:5b # vandy (anything)
112 .It 8::9:1:C6:75 SYSHPBSD,SYSHPUX # jaguar (either)
116 logs status and error messages via
118 A startup message is always logged, and in the case of fatal errors (or
119 deadly signals) a message is logged announcing the server's termination.
120 In general, a non-fatal error is handled by ignoring the event that caused
121 it (e.g. an invalid Ethernet address in the config file causes that line
124 The following signals have the specified effect when sent to the server
128 .Bl -tag -width SIGUSR1 -offset -compact
130 Drop all active connections and reconfigure.
132 Turn on debugging, do nothing if already on.
134 Turn off debugging, do nothing if already off.
137 .Bl -tag -width /usr/libexec/rbootd -compact
145 directory containing boot files
146 .It /var/run/rbootd.pid
155 If multiple servers are started on the same interface, each will receive
156 and respond to the same boot packets.