1.\" $NetBSD: mopd.8,v 1.4 2002/01/19 03:37:38 wiz 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 Ar interface 39.Sh DESCRIPTION 40.Nm 41services MOP Load requests on the Ethernet connected to 42.Ar interface 43or all interfaces if 44.Sq Fl a 45is given. 46In a load request received by 47.Nm 48a filename can be given. This is the normal case for e.g. terminal servers. 49If a filename isn't given 50.Nm 51must know what image to load. 52.Pp 53Upon receiving a request, 54.Nm 55checks if the requested file exists in 56.Pa /tftpboot/mop , 57the filename is normaly uppercase and with an extension of 58.Pa .SYS . 59If the filename isn't given, the ethernet address of the target is used as 60filename, e.g. 61.Pa 08002b09f4de.SYS 62and it might be a soft link to another file. 63.Pp 64.Nm 65supports two kinds of files. The first type that is check is if the file is 66in 67.Xr a.out 5 68format. If not, a couple of Digital's formats are checked. 69.Pp 70In normal operation, 71.Nm 72forks a copy of itself and runs in 73the background. Anomalies and errors are reported via 74.Xr syslog 3 . 75.Sh OPTIONS 76.Bl -tag -width indent 77.It Fl a 78Listen on all the Ethernets attached to the system. 79If 80.Sq Fl a 81is omitted, an interface must be specified. 82.It Fl d 83Run in debug mode, with all the output to stdout. The process will run in 84the foreground. 85.It Fl f 86Run in the foreground. 87.El 88.Sh FILES 89.Bl -tag -width Pa -compact 90.It Pa /tftpboot/mop 91.El 92.Sh SEE ALSO 93.Xr mopa.out 1 , 94.Xr mopchk 1 , 95.Xr mopprobe 1 , 96.Xr moptrace 1 , 97.Xr bpf 4 98.Rs 99DECnet Digital Network Architecture Phase IV, 100.%R Maintenance Operations Functional Specification V3.0.0 101.%N AA-X436A-TK 102.Re 103.Rs 104DECnet Digital Network Architecture, 105.%R Maintenance Operations Protocol Functional Specification V4.0.0 106.%N EK-DNA11-FS-001 107.Re 108.Sh AUTHORS 109Mats O Jansson (moj@stacken.kth.se). 110