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. Neither the name of the University nor the names of its contributors
21 .\" may be used to endorse or promote products derived from this software
22 .\" without specific prior written permission.
24 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
25 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
26 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
27 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
28 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
29 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
30 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
31 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
32 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
33 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
36 .\" from: @(#)rbootd.8 8.2 (Berkeley) 12/11/93
37 .\" $FreeBSD: src/libexec/rbootd/rbootd.8,v 1.9.2.3 2001/03/05 18:21:59 ru Exp $
39 .\" Utah Hdr: rbootd.man 3.1 92/07/06
40 .\" Author: Jeff Forys, University of Utah CSS
47 .Nd HP remote boot server
56 utility services boot requests from Hewlett-Packard workstations over a
58 All boot files must reside in the boot file directory; further, if a
59 client supplies path information in its boot request, it will be silently
60 stripped away before processing.
63 only responds to requests from machines listed in its configuration file.
65 The options are as follows:
66 .Bl -tag -width indent
68 Respond to boot requests from any machine.
69 The configuration file is ignored if this option is specified.
74 Packets sent and received are displayed to the terminal.
76 Service boot requests on specified interface.
79 searches the system interface list for the lowest numbered, configured
80 ``up'' interface (excluding loopback).
81 Ties are broken by choosing the earliest match.
86 on the command line causes
88 to use a different configuration file from the default.
90 The configuration file is a text file where each line describes a particular
92 A line must start with a machine's Ethernet address followed by an optional
93 list of boot file names.
94 An Ethernet address is specified in hexadecimal with each of its six octets
96 The boot file names come from the boot file directory.
97 The ethernet address and boot file(s) must be separated by white-space
98 and/or comma characters.
99 A pound sign causes the remainder of a line to be ignored.
101 Here is a sample configuration file:
104 # ethernet addr boot file(s) comments
106 08:00:09:0:66:ad SYSHPBSD # snake (4.3BSD)
107 08:00:09:0:59:5b # vandy (anything)
108 8::9:1:C6:75 SYSHPBSD,SYSHPUX # jaguar (either)
113 utility logs status and error messages via
115 A startup message is always logged, and in the case of fatal errors (or
116 deadly signals) a message is logged announcing the server's termination.
117 In general, a non-fatal error is handled by ignoring the event that caused
118 it (e.g. an invalid Ethernet address in the config file causes that line
121 The following signals have the specified effect when sent to the server
125 .Bl -tag -width SIGUSR1 -offset xxxxxxxx
127 Drop all active connections and reconfigure.
129 Turn on debugging, do nothing if already on.
131 Turn off debugging, do nothing if already off.
134 .Bl -tag -width /usr/libexec/rbootd -compact
137 .It Pa /etc/rbootd.conf
139 .It Pa /tmp/rbootd.dbg
141 .It Pa /usr/mdec/rbootd
142 directory containing boot files
143 .It Pa /var/run/rbootd.pid
152 If multiple servers are started on the same interface, each will receive
153 and respond to the same boot packets.