.\" Copyright (c) 1988, 1992 The University of Utah and the Center
.\" for Software Science (CSS).
.\" Copyright (c) 1992, 1993
.\" The Regents of the University of California. All rights reserved.
.\" This code is derived from software contributed to Berkeley by
.\" the Center for Software Science of the University of Utah Computer
.\" Science Department. CSS requests users of this software to return
.\" to css-dist@cs.utah.edu any improvements that they make and grant
.\" CSS redistribution rights.
.\" %sccs.include.redist.roff%
.\" @(#)rbootd.8 8.1 (Berkeley) %G%
.\" Utah $Hdr: rbootd.man 3.1 92/07/06$
.\" Author: Jeff Forys, University of Utah CSS
.Nd HP remote boot server
utility services boot requests from Hewlett-Packard workstations over a
All boot files must reside in the boot file directory; further, if a
client supplies path information in its boot request, it will be silently
stripped away before processing.
only responds to requests from machines listed in its configuration file.
The options are as follows:
Respond to boot requests from any machine.
The configuration file is ignored if this option is specified.
Packets sent and received are displayed to the terminal.
Service boot requests on specified interface.
searches the system interface list for the lowest numbered, configured
``up'' interface (excluding loopback).
Ties are broken by choosing the earliest match.
on the command line causes
to use a different configuration file from the default.
The configuration file is a text file where each line describes a particular
A line must start with a machine's Ethernet address followed by an optional
An ethernet address is specified in hexadecimal with each of its six octets
The boot file names come from the boot file directory.
The ethernet address and boot file(s) must be separated by white-space
A pound sign causes the remainder of a line to be ignored.
Here is a sample configuration file:
.Bl -column 08:00:09:0:66:ad SYSHPBSD,SYSHPUX "# vandy (anything)"
.It # ethernet addr boot file(s) comments
.It 08:00:09:0:66:ad SYSHPBSD # snake (4.3BSD)
.It 08:00:09:0:59:5b # vandy (anything)
.It 8::9:1:C6:75 SYSHPBSD,SYSHPUX # jaguar (either)
logs status and error messages via
A startup message is always logged, and in the case of fatal errors (or
deadly signals) a message is logged announcing the server's termination.
In general, a non-fatal error is handled by ignoring the event that caused
it (e.g. an invalid Ethernet address in the config file causes that line
The following signals have the specified effect when sent to the server
.Bl -tag -width SIGUSR1 -offset -compact
Drop all active connections and reconfigure.
Turn on debugging, do nothing if already on.
Turn off debugging, do nothing if already off.
.Bl -tag -width /usr/libexec/rbootd -compact
directory containing boot files
If multiple servers are started on the same interface, each will receive
and respond to the same boot packets.