Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

mopd(8) [netbsd man page]

MOPD(8) 						    BSD System Manager's Manual 						   MOPD(8)

NAME
mopd -- Maintenance Operations Protocol (MOP) Loader Daemon SYNOPSIS
mopd [-adf] [-s mopdir] [interface] [...] DESCRIPTION
mopd services DEC Maintenance Operations Protocol (MOP) Load requests on the Ethernet connected to interface or all interfaces if -a option is given. In a load request received by mopd a filename can be given by the client. This is the normal case for terminal servers. If a filename isn't in the client load request mopd must know what image to load. Upon receiving a request, mopd checks if the requested file exists in /tftpboot/mop (unless the -s option is given, see below) the filename is normally uppercase and with an extension of .SYS. If the filename isn't given, the ethernet address of the target is used as filename, e.g. 08002b09f4de.SYS and it might be a soft link to another file. mopd supports two kinds of files. The first type that is check is if the file is in a.out(5) format. If not, a couple of Digital's formats are checked. In normal operation, mopd forks a copy of itself and runs in the background. Anomalies and errors are reported via syslog(3). OPTIONS
-a Listen on all the Ethernets attached to the system. If -a is omitted, an interface must be specified. -d Run in debug mode, with all the output to stdout. The process will run in the foreground. -f Run in the foreground. -s Change the directory to look for files in from /tftpboot/mop to mopdir. FILES
/tftpboot/mop NOTES
mopd automatically appends an upper case .SYS to the filename provided by the client. The typical client sends the requested file name in upper case. SEE ALSO
mopchk(1), mopcopy(1), mopprobe(1), moptrace(1), bpf(4) DECnet Digital Network Architecture Phase IV, Maintenance Operations Functional Specification V3.0.0, AA-X436A-TK. DECnet Digital Network Architecture, Maintenance Operations Protocol Functional Specification V4.0.0, EK-DNA11-FS-001. AUTHORS
Mats O Jansson <moj@stacken.kth.se> BSD
January 23, 2004 BSD

Check Out this Related Man Page

RARP(8) 						     Linux Programmer's Manual							   RARP(8)

NAME
rarpd - Reverse Address Resolution Protocol (RARP) daemon SYNOPSIS
rarpd [-aAvode] [-b bootdir] [interface] DESCRIPTION
Rarpd is a daemon which responds to RARP requests. RARP is used by some machines at boot time to discover their IP address. They provide their Ethernet address and rarpd responds with their IP address if it finds it in the ethers database (either /etc/ethers file or NIS+ lookup) and using DNS lookup if ethers database contains a hostname and not an IP address. By default rarpd also checks if a bootable image with a name starting with the IP address in hexadecimal uppercase letters is present in the TFTP boot directory (usually /tftpboot ) before it decides to respond to the RARP request. The optional argument interface restricts the daemon instance to access only the indicated network interface. Only a single name is possi- ble. OPTIONS
-a Do not bind to the interface. -A Respond to ARP as well as RARP requests. -v Tell the user what is going on by being verbose. -d Debugging mode. Do not detach from the tty. This also implies verbose mode. -e Skip the check for bootable image in the TFTP boot directory. If not present, then even if the Ethernet address is present in the ethers database but the bootable image for the resolved IP does not exist, rarpd will not respond to the request. -o Accept offlink packages on the active interfaces. -b bootdir Access bootdir instead of the default /tftpboot as the TFTP boot directory for bootable image checks. OBSOLETES
This daemon rarpd obsoletes kernel rarp daemon present in Linux kernels up to 2.2 which was controlled by the rarp(8) command. SIGNALS
SIGHUP Renew the internal address list, which records IPv4 addresses available at each active network interface. The restriction set by the command line argument interface is still in effect, if in use. FILES
/etc/ethers, /etc/nsswitch.conf, /tftpboot SEE ALSO
ethers(5) AUTHORS
Alexey Kuznetsov, <kuznet@ms2.inr.ac.ru> Jakub Jelinek, <jakub@redhat.com> rarpd 7 April 2000 RARP(8)
Man Page