xref: /netbsd/usr.sbin/mopd/mopd/mopd.8 (revision c4a72b64)
1.\"	$NetBSD: mopd.8,v 1.8 2002/11/05 14:18:04 thorpej Exp $
2.\"
3.\" Copyright (c) 1993-96 Mats O Jansson.  All rights reserved.
4.\"
5.\" Redistribution and use in source and binary forms, with or without
6.\" modification, are permitted provided that the following conditions
7.\" are met:
8.\" 1. Redistributions of source code must retain the above copyright
9.\"    notice, this list of conditions and the following disclaimer.
10.\" 2. Redistributions in binary form must reproduce the above copyright
11.\"    notice, this list of conditions and the following disclaimer in the
12.\"    documentation and/or other materials provided with the distribution.
13.\" 3. All advertising materials mentioning features or use of this software
14.\"    must display the following acknowledgement:
15.\"	This product includes software developed by Mats O Jansson.
16.\" 4. The name of the author may not be used to endorse or promote products
17.\"    derived from this software without specific prior written permission.
18.\"
19.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
20.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
21.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
22.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
23.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
24.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
25.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
26.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
27.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
28.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
29.\"
30.Dd September 24, 1995
31.Dt MOPD 8
32.Sh NAME
33.Nm mopd
34.Nd MOP Loader Daemon
35.Sh SYNOPSIS
36.Nm
37.Op Fl adf
38.Op Fl s Ar mopdir
39.Op Ar interface
40.Op Ar ...
41.Sh DESCRIPTION
42.Nm
43services MOP Load requests on the Ethernet connected to
44.Ar interface
45or all interfaces if
46.Sq Fl a
47is given.
48In a load request received by
49.Nm
50a filename can be given. This is the normal case for e.g. terminal servers.
51If a filename isn't given
52.Nm
53must know what image to load.
54.Pp
55Upon receiving a request,
56.Nm
57checks if the requested file exists in
58.Pa /tftpboot/mop
59(unless the
60.Fl s
61option is given, see below) the filename is normally uppercase and with an
62extension of
63.Pa .SYS .
64If the filename isn't given, the ethernet address of the target is used as
65filename, e.g.
66.Pa 08002b09f4de.SYS
67and it might be a soft link to another file.
68.Pp
69.Nm
70supports two kinds of files. The first type that is check is if the file is
71in
72.Xr a.out 5
73format. If not, a couple of Digital's formats are checked.
74.Pp
75In normal operation,
76.Nm
77forks a copy of itself and runs in
78the background.  Anomalies and errors are reported via
79.Xr syslog 3 .
80.Sh OPTIONS
81.Bl -tag -width indent
82.It Fl a
83Listen on all the Ethernets attached to the system.
84If
85.Sq Fl a
86is omitted, an interface must be specified.
87.It Fl d
88Run in debug mode, with all the output to stdout. The process will run in
89the foreground.
90.It Fl f
91Run in the foreground.
92.It Fl s
93Change the directory to look for files in from
94.Pa /tftpboot/mop
95to
96.Ar mopdir .
97.El
98.Sh FILES
99.Bl -tag -width Pa -compact
100.It Pa /tftpboot/mop
101.El
102.Sh SEE ALSO
103.Xr mopchk 1 ,
104.Xr mopcopy 1 ,
105.Xr mopprobe 1 ,
106.Xr moptrace 1 ,
107.Xr bpf 4
108.Rs
109DECnet Digital Network Architecture Phase IV,
110.%R Maintenance Operations Functional Specification V3.0.0
111.%N AA-X436A-TK
112.Re
113.Rs
114DECnet Digital Network Architecture,
115.%R Maintenance Operations Protocol Functional Specification V4.0.0
116.%N EK-DNA11-FS-001
117.Re
118.Sh AUTHORS
119.An Mats O Jansson Aq moj@stacken.kth.se
120