xref: /original-bsd/libexec/rbootd/rbootd.8 (revision b4971bb3)
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.
5.\"
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.
11.\"
12.\" %sccs.include.redist.roff%
13.\"
14.\"	@(#)rbootd.8	8.1 (Berkeley) 06/04/93
15.\"
16.\" Utah $Hdr: rbootd.man 3.1 92/07/06$
17.\" Author: Jeff Forys, University of Utah CSS
18.\"
19.Dd ""
20.Dt RBOOTD 8
21.Os
22.Sh NAME
23.Nm rbootd
24.Nd HP remote boot server
25.Sh SYNOPSIS
26.Nm rbootd
27.Op Fl ad
28.Op Fl i Ar interface
29.Op config_file
30.Sh DESCRIPTION
31The
32.Nm rbootd
33utility services boot requests from Hewlett-Packard workstations over a
34local area network.
35All boot files must reside in the boot file directory; further, if a
36client supplies path information in its boot request, it will be silently
37stripped away before processing.
38By default,
39.Nm rbootd
40only responds to requests from machines listed in its configuration file.
41.Pp
42The options are as follows:
43.Bl -tag -width Fl
44.It Fl a
45Respond to boot requests from any machine.
46The configuration file is ignored if this option is specified.
47.It Fl d
48Run
49.Nm rbootd
50in debug mode.
51Packets sent and received are displayed to the terminal.
52.It Fl i Ar interface
53Service boot requests on specified interface.
54If unspecified,
55.Nm rbootd
56searches the system interface list for the lowest numbered, configured
57``up'' interface (excluding loopback).
58Ties are broken by choosing the earliest match.
59.El
60.Pp
61Specifying
62.Ar config_file
63on the command line causes
64.Nm rbootd
65to use a different configuration file from the default.
66.Pp
67The configuration file is a text file where each line describes a particular
68machine.
69A line must start with a machine's Ethernet address followed by an optional
70list of boot file names.
71An ethernet address is specified in hexadecimal with each of its six octets
72separated by a colon.
73The boot file names come from the boot file directory.
74The ethernet address and boot file(s) must be separated by white-space
75and/or comma characters.
76A pound sign causes the remainder of a line to be ignored.
77.Pp
78Here is a sample configuration file:
79.Bl -column 08:00:09:0:66:ad SYSHPBSD,SYSHPUX "# vandy (anything)"
80.It #
81.It # ethernet addr	boot file(s)	comments
82.It #
83.It 08:00:09:0:66:ad	SYSHPBSD	# snake (4.3BSD)
84.It 08:00:09:0:59:5b		# vandy (anything)
85.It 8::9:1:C6:75	SYSHPBSD,SYSHPUX	# jaguar (either)
86.El
87.Pp
88.Nm Rbootd
89logs status and error messages via
90.Xr syslog 3 .
91A startup message is always logged, and in the case of fatal errors (or
92deadly signals) a message is logged announcing the server's termination.
93In general, a non-fatal error is handled by ignoring the event that caused
94it (e.g. an invalid Ethernet address in the config file causes that line
95to be invalidated).
96.Pp
97The following signals have the specified effect when sent to the server
98process using the
99.Xr kill 1
100command:
101.Bl -tag -width SIGUSR1 -offset -compact
102.It SIGHUP
103Drop all active connections and reconfigure.
104.It SIGUSR1
105Turn on debugging, do nothing if already on.
106.It SIGUSR2
107Turn off debugging, do nothing if already off.
108.El
109.Sh "FILES"
110.Bl -tag -width /usr/libexec/rbootd -compact
111.It /dev/bpf#
112packet-filter device
113.It /etc/rbootd.conf
114configuration file
115.It /tmp/rbootd.dbg
116debug output
117.It /usr/mdec/rbootd
118directory containing boot files
119.It /var/run/rbootd.pid
120process id
121.El
122.Sh SEE ALSO
123.Xr kill 1 ,
124.Xr socket 2 ,
125.Xr signal 3 ,
126.Xr syslog 3 ,
127.Xr rmp 4
128.Sh BUGS
129If multiple servers are started on the same interface, each will receive
130and respond to the same boot packets.
131