From fcb857d64dec83592582c1d4e08d0770e21ebdff Mon Sep 17 00:00:00 2001 From: CSRG Date: Wed, 21 Jul 1993 21:16:18 -0800 Subject: [PATCH] BSD 4_4 development Work on file usr/share/man/cat8/rbootd.0 Synthesized-from: CSRG/cd3/4.4 --- usr/share/man/cat8/rbootd.0 | 84 +++++++++++++++++++++++++++++++++++++ 1 file changed, 84 insertions(+) create mode 100644 usr/share/man/cat8/rbootd.0 diff --git a/usr/share/man/cat8/rbootd.0 b/usr/share/man/cat8/rbootd.0 new file mode 100644 index 0000000000..049b01e1d1 --- /dev/null +++ b/usr/share/man/cat8/rbootd.0 @@ -0,0 +1,84 @@ +RBOOTD(8) BSD System Manager's Manual RBOOTD(8) + +NNAAMMEE + rrbboooottdd - HP remote boot server + +SSYYNNOOPPSSIISS + rrbboooottdd [--aadd] [--ii _i_n_t_e_r_f_a_c_e] [config_file] + +DDEESSCCRRIIPPTTIIOONN + The rrbboooottdd 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, rrbboooottdd only responds to requests from machines listed in its + configuration file. + + The options are as follows: + + --aa Respond to boot requests from any machine. The configuration + file is ignored if this option is specified. + + --dd Run rrbboooottdd in debug mode. Packets sent and received are dis- + played to the terminal. + + --ii _i_n_t_e_r_f_a_c_e + Service boot requests on specified interface. If unspeci- + fied, rrbboooottdd searches the system interface list for the low- + est numbered, configured ``up'' interface (excluding loop- + back). Ties are broken by choosing the earliest match. + + Specifying _c_o_n_f_i_g___f_i_l_e on the command line causes rrbboooottdd 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- + nored. + + 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) + + RRbboooottdd 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 inval- + idated). + + 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. + +FFIILLEESS + /dev/bpf# packet-filter device + /etc/rbootd.conf configuration file + /tmp/rbootd.dbg debug output + /usr/mdec/rbootd directory containing boot files + /var/run/rbootd.pid process id + +SSEEEE AALLSSOO + kill(1), socket(2), signal(3), syslog(3), rmp(4) + +BBUUGGSS + If multiple servers are started on the same interface, each will receive + and respond to the same boot packets. + +4.4BSD June 4, 1993 2 -- 2.20.1