1.\" $NetBSD: mopd.8,v 1.14 2009/10/20 00:51:13 snj 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.\" 14.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR 15.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES 16.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. 17.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, 18.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 19.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 20.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 21.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 22.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF 23.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 24.\" 25.Dd January 23, 2004 26.Dt MOPD 8 27.Os 28.Sh NAME 29.Nm mopd 30.Nd Maintenance Operations Protocol (MOP) Loader Daemon 31.Sh SYNOPSIS 32.Nm 33.Op Fl adf 34.Op Fl s Ar mopdir 35.Op Ar interface 36.Op Ar ... 37.Sh DESCRIPTION 38.Nm 39services 40.Tn DEC 41Maintenance Operations Protocol 42.Pq Tn MOP 43Load requests on the Ethernet connected to 44.Ar interface 45or all interfaces if 46.Fl a 47option is given. 48.Pp 49In a load request received by 50.Nm 51a filename can be given by the client. 52This is the normal case for terminal servers. 53If a filename isn't in the client load request 54.Nm 55must know what image to load. 56.Pp 57Upon receiving a request, 58.Nm 59checks if the requested file exists in 60.Pa /tftpboot/mop 61(unless the 62.Fl s 63option is given, see below) the filename is normally uppercase and with an 64extension of 65.Pa .SYS . 66If the filename isn't given, the ethernet address of the target is used as 67filename, e.g. 68.Pa 08002b09f4de.SYS 69and it might be a soft link to another file. 70.Pp 71.Nm 72supports two kinds of files. 73The first type that is check is if the file is in 74.Xr a.out 5 75format. 76If not, a couple of Digital's formats are checked. 77.Pp 78In normal operation, 79.Nm 80forks a copy of itself and runs in the background. 81Anomalies and errors are reported via 82.Xr syslog 3 . 83.Sh OPTIONS 84.Bl -tag -width indent 85.It Fl a 86Listen on all the Ethernets attached to the system. 87If 88.Fl a 89is omitted, an interface must be specified. 90.It Fl d 91Run in debug mode, with all the output to stdout. 92The process will run in the foreground. 93.It Fl f 94Run in the foreground. 95.It Fl s 96Change the directory to look for files in from 97.Pa /tftpboot/mop 98to 99.Ar mopdir . 100.El 101.Sh FILES 102.Bl -tag -width Pa -compact 103.It Pa /tftpboot/mop 104.El 105.Sh NOTES 106.Nm 107automatically appends an upper case 108.Pa .SYS 109to the filename provided by the client. 110The typical client sends the requested file name in upper case. 111.Sh SEE ALSO 112.Xr mopchk 1 , 113.Xr mopcopy 1 , 114.Xr mopprobe 1 , 115.Xr moptrace 1 , 116.Xr bpf 4 117.Rs 118.%J DECnet Digital Network Architecture Phase IV 119.%R Maintenance Operations Functional Specification V3.0.0 120.%N AA-X436A-TK 121.Re 122.Rs 123.%J DECnet Digital Network Architecture 124.%R Maintenance Operations Protocol Functional Specification V4.0.0 125.%N EK-DNA11-FS-001 126.Re 127.Sh AUTHORS 128.An Mats O Jansson Aq moj@stacken.kth.se 129