BSD 4_3_Net_2 release

[unix-history] / usr / src / share / man / man8 / man8.hp300 / rbootd.8

diff --git a/usr/src/share/man/man8/man8.hp300/rbootd.8 b/usr/src/share/man/man8/man8.hp300/rbootd.8
index a3d4043..b62e344 100644 (file)
--- a/usr/src/share/man/man8/man8.hp300/rbootd.8
+++ b/usr/src/share/man/man8/man8.hp300/rbootd.8
@@ -1,124 +1,150 @@
-.\" Copyright (c) 1990 The Regents of the University of California.
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.

 .\" All rights reserved.
 .\"
 .\" This code is derived from software contributed to Berkeley by
 .\" the Systems Programming Group of the University of Utah Computer
 .\" All rights reserved.
 .\"
 .\" This code is derived from software contributed to Berkeley by
 .\" the Systems Programming Group of the University of Utah Computer

+.\"

 .\" Science Department.
 .\" Science Department.

+.\" 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.

 .\"
 .\"

-.\" Redistribution and use in source and binary forms are permitted provided
-.\" that: (1) source distributions retain this entire copyright notice and
-.\" comment, and (2) distributions including binaries display the following
-.\" acknowledgement:  ``This product includes software developed by the
-.\" University of California, Berkeley and its contributors'' in the
-.\" documentation or other materials provided with the distribution and in
-.\" all advertising materials mentioning features or use of this software.
-.\" 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 ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED
-.\" WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
-.\" MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
+.\" 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    5.1 (Berkeley) 6/29/90
+.\"     @(#)rbootd.8   5.4 (Berkeley) 8/5/91

 .\"
 .\"

-.TH RBOOTD 8 "June 29, 1990"
-.UC 7
-.SH NAME
-rbootd \- HP remote boot server
-.SH SYNOPSIS
-.B rbootd
-[\-a] [\-d] [ConfigFile]
-.SH DESCRIPTION
-.I Rbootd
+.Dd August 5, 1991
+.Dt RBOOTD 8
+.Os
+.Sh NAME
+.Nm rbootd
+.Nd
+.Tn HP
+remote boot server
+.Sh SYNOPSIS
+.Nm rbootd
+.Op Fl a
+.Op Fl d
+.Op Ar ConfigFile
+.Sh DESCRIPTION
+.Nm Rbootd

 services boot requests from Hewlett-Packard workstations 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,
 services boot requests from Hewlett-Packard workstations 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,

-.I rbootd
+.Nm rbootd

 only responds to requests from machines listed in its configuration
 file.
 only responds to requests from machines listed in its configuration
 file.

-.PP
-.I Rbootd
+.Pp
+.Nm Rbootd

 supports the following command line options:
 supports the following command line options:

-.TP
-.B \-a
+.Bl -tag -width Ds
+.It Fl a

 Respond to boot requests from any machine.  With this option,
 the configuration file is ignored.
 Respond to boot requests from any machine.  With this option,
 the configuration file is ignored.

-.TP
-.B \-d
+.It Fl d

 Run server in debug mode.  Packets sent and
 received are displayed to the terminal.
 Run server in debug mode.  Packets sent and
 received are displayed to the terminal.

-.TP
-.B ConfigFile
+.It Ar ConfigFile

 Specify a different configuration file.
 Specify a different configuration file.

-.PP
+.El
+.Pp

 The configuration file consists of ascii text where each line describes
 a particular machine.  A line must start with a machines'
 The configuration file consists of ascii text where each line describes
 a particular machine.  A line must start with a machines'

-.I ethernet address
+.Em ethernet address

 followed by an optional list of
 followed by an optional list of

-.I boot file names.
+.Em 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 ethernet address and boot file(s) must be separated
 by white-space and/or commas.  A pound sign causes the remainder of
 a line to be ignored.  Here is a sample configuration file:
 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 ethernet address and boot file(s) must be separated
 by white-space and/or commas.  A pound sign causes the remainder of
 a line to be ignored.  Here is a sample configuration file:

-.in +4
-.nf
-
-.ta \w'08:00:09:01:C6:75  'u +\w'SYSHPBSD,SYSHPUX  'u +\w'# jaguar (either)'u
+.Bd -literal

 #
 #

-# ethernet addr        boot file(s)    comments
+# 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)
-.DT
-.fi
-.in
-.PP
-.I Rbootd
+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)
+.Ed
+.Pp
+.Nm Rbootd

 logs status and error messages via
 logs status and error messages via

-.I syslog.
+.Xr syslog .

 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).
 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).

-.PP
+.Pp

 The following signals have the specified effect when sent to
 The following signals have the specified effect when sent to

-the server process using the kill(1) command.
-.IP SIGHUP
+the server process using the
+.Xr kill 1
+command.
+.Bl -tag -width Fl
+.It Dv SIGHUP

 Drop all active connections and reconfigure.
 Drop all active connections and reconfigure.

-.IP SIGUSR1
-Turn on debugging, do nothing if already on.  (SIGEMT on older systems
-without SIGUSR1)
-.IP SIGUSR2
-Turn off debugging, do nothing if already off.  (SIGFPE on older systems
-without SIGUSR2)
-.SH "FILES"
-.PD 0
-.TP 22
-/etc/rbootd.conf
+.It Dv SIGUSR1
+Turn on debugging, do nothing if already on.
+.Pf ( Dv SIGEMT
+on older systems
+without
+.Dv SIGUSR1 )
+.It Dv SIGUSR2
+Turn off debugging, do nothing if already off.
+.Pf ( Dv SIGFPE
+on older systems
+without
+.Dv SIGUSR2 )
+.Sh FILES
+.Bl -tag -width /usr/tmp/rbootd.dbgxx -compact
+.It Pa /etc/rbootd.conf

 configuration file
 configuration file

-.TP
-/usr/lib/rbootd
+.It Pa /usr/lib/rbootd

 directory containing boot files
 directory containing boot files

-.TP
-/etc/rbootd.pid
+.It Pa /etc/rbootd.pid

 process id
 process id

-.TP
-/usr/tmp/rbootd.dbg
+.It Pa /usr/tmp/rbootd.dbg

 debug output
 debug output

-.PD
-.SH "SEE ALSO"
-kill(1), socket(2), signal(3C), syslog(3), rmp(4)
-.SH "AUTHOR"
+.El
+.Sh SEE ALSO
+.Xr kill 1 ,
+.Xr socket 2 ,
+.Xr signal 3 ,
+.Xr syslog 3 ,
+.Xr rmp 4
+.Sh AUTHOR

 Jeff Forys, University of Utah
 Jeff Forys, University of Utah

-.SH "BUGS"
-.TP 2
-\-
+.Sh BUGS

 If more than one server is started, both will receive and respond
 to the same boot packets.
 If more than one server is started, both will receive and respond
 to the same boot packets.

+.Sh HISTORY
+The
+.Nm
+command is
+.Ud