.\" 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..\".\" Redistribution and use in source and binary forms, with or without.\" modification, are permitted provided that the following conditions.\" are met:.\" 1. Redistributions of source code must retain the above copyright.\"    notice, this list of conditions and the following disclaimer..\" 2. Redistributions in binary form must reproduce the above copyright.\"    notice, this list of conditions and the following disclaimer in the.\"    documentation and/or other materials provided with the distribution..\" 3. All advertising materials mentioning features or use of this software.\"    must display the following acknowledgement:.\"	This product includes software developed by the University of.\"	California, Berkeley and its contributors..\" 4. Neither the name of the University nor the names of its contributors.\"    may be used to endorse or promote products derived from this software.\"    without specific prior written permission..\".\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION).\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF.\" SUCH DAMAGE..\".\"	@(#)rbootd.8	8.2 (Berkeley) 12/11/93.\".\" Utah $Hdr: rbootd.man 3.1 92/07/06$.\" Author: Jeff Forys, University of Utah CSS.\".Dd "December 11, 1993".Dt RBOOTD 8.Os.Sh NAME.Nm rbootd.Nd HP remote boot server.Sh SYNOPSIS.Nm rbootd.Op Fl ad.Op Fl i Ar interface.Op config_file.Sh DESCRIPTIONThe.Nm rbootdutility services boot requests from Hewlett-Packard workstations over alocal area network.All boot files must reside in the boot file directory; further, if aclient supplies path information in its boot request, it will be silentlystripped away before processing.By default,.Nm rbootdonly responds to requests from machines listed in its configuration file..PpThe options are as follows:.Bl -tag -width Fl.It Fl aRespond to boot requests from any machine.The configuration file is ignored if this option is specified..It Fl dRun.Nm rbootdin debug mode.Packets sent and received are displayed to the terminal..It Fl i Ar interfaceService boot requests on specified interface.If unspecified,.Nm rbootdsearches the system interface list for the lowest numbered, configured``up'' interface (excluding loopback).Ties are broken by choosing the earliest match..El.PpSpecifying.Ar config_fileon the command line causes.Nm rbootdto use a different configuration file from the default..PpThe configuration file is a text file where each line describes a particularmachine.A line must start with a machine's Ethernet address followed by an optionallist of boot file names.An Ethernet address is specified in hexadecimal with each of its six octetsseparated by a colon.The boot file names come from the boot file directory.The ethernet address and boot file(s) must be separated by white-spaceand/or comma characters.A pound sign causes the remainder of a line to be ignored..PpHere is a sample configuration file:.Bl -column 08:00:09:0:66:ad SYSHPBSD,SYSHPUX "# vandy (anything)".It #.It # ethernet addr	boot file(s)	comments.It #.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).El.Pp.Nm Rbootdlogs status and error messages via.Xr syslog 3 .A startup message is always logged, and in the case of fatal errors (ordeadly signals) a message is logged announcing the server's termination.In general, a non-fatal error is handled by ignoring the event that causedit (e.g. an invalid Ethernet address in the config file causes that lineto be invalidated)..PpThe following signals have the specified effect when sent to the serverprocess using the.Xr kill 1command:.Bl -tag -width SIGUSR1 -offset -compact.It SIGHUPDrop all active connections and reconfigure..It SIGUSR1Turn on debugging, do nothing if already on..It SIGUSR2Turn off debugging, do nothing if already off..El.Sh "FILES".Bl -tag -width /usr/libexec/rbootd -compact.It /dev/bpf#packet-filter device.It /etc/rbootd.confconfiguration file.It /tmp/rbootd.dbgdebug output.It /usr/mdec/rbootddirectory containing boot files.It /var/run/rbootd.pidprocess id.El.Sh SEE ALSO.Xr kill 1 ,.Xr socket 2 ,.Xr signal 3 ,.Xr syslog 3 ,.Xr rmp 4.Sh BUGSIf multiple servers are started on the same interface, each will receiveand respond to the same boot packets.