Skip site navigation (1)Skip section navigation (2)

FreeBSD Manual Pages


home | help
RBOOTD(8)		FreeBSD	System Manager's Manual		     RBOOTD(8)

     rbootd -- HP remote boot server

     rbootd [-ad] [-i interface] [config_file]

     The rbootd	utility	services boot requests from Hewlett-Packard worksta-
     tions over	a local	area network.  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.	 By
     default, rbootd only responds to requests from machines listed in its
     configuration file.

     The options are as	follows:

     -a	     Respond to	boot requests from any machine.	 The configuration
	     file is ignored if	this option is specified.

     -d	     Run rbootd	in debug mode.	Packets	sent and received are dis-
	     played to the terminal.

     -i	interface
	     Service boot requests on specified	interface.  If unspecified,
	     rbootd searches the system	interface list for the lowest num-
	     bered, configured ``up'' interface	(excluding loopback).  Ties
	     are broken	by choosing the	earliest match.

     Specifying	config_file on the command line	causes rbootd to use a differ-
     ent configuration file from the default.

     The configuration file is a text file where each line describes a partic-
     ular machine.  A line must	start with a machine's Ethernet	address	fol-
     lowed by an optional list of boot file names.  An Ethernet	address	is
     specified in hexadecimal with each	of its six octets separated by a
     colon.  The boot file names come from the boot file directory.  The eth-
     ernet address and boot file(s) must be separated by white-space and/or
     comma characters.	A pound	sign causes the	remainder of a line to be ig-

     Here is a sample configuration file:

     # ethernet	addr	 boot file(s)	     comments
     08:00:09:0:66:ad	 SYSHPBSD	     # snake (4.3BSD)
     08:00:09:0:59:5b			     # vandy (anything)
     8::9:1:C6:75	 SYSHPBSD,SYSHPUX    # jaguar (either)

     The rbootd	utility	logs status and	error messages via syslog(3).  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 to be invalidated).

     The following signals have	the specified effect when sent to the server
     process using the kill(1) command:

	     SIGHUP   Drop all active connections and reconfigure.

	     SIGUSR1  Turn on debugging, do nothing if already on.

	     SIGUSR2  Turn off debugging, do nothing if	already	off.

     /dev/bpf#		  packet-filter	device
     /etc/rbootd.conf	  configuration	file
     /tmp/rbootd.dbg	  debug	output
     /usr/mdec/rbootd	  directory containing boot files
     /var/run/  process id

     kill(1), socket(2), signal(3), syslog(3)

     If	multiple servers are started on	the same interface, each will receive
     and respond to the	same boot packets.

FreeBSD	13.0		       December	11, 1993		  FreeBSD 13.0


Want to link to this manual page? Use this URL:

home | help