NAME
pvmd3 - PVM version 3 daemon
SYNOPSIS
pvmd [ -options ] [ hostfile ] &
DESCRIPTION
Pvmd3 is a daemon process which coordinates unix hosts in a virtual machine. One pvmd3 must run on each host in the group. They provide the communication and process control functions needed by the user's PVM processes. The daemon can be started manually with a host file argument that will automatically start the remote pvmds. The local and remote pvmds can also be started from the PVM console program pvm.
The name of the daemon executable is pvmd3. It is usually started by a shell script, $PVM_ROOT/lib/pvmd.
OPTIONS
The following options may be specified on the command line when starting the master pvmd or PVM console:
-dmask Set pvmd debug mask. Used to debug the pvmd or libpvm (not intended to be used to debug application programs). Mask is a hexadecimal number which is the sum of the following bits: Bit Information
The following options are used by the master pvmd when starting slaves and are only of interest to someone writing a hoster. Don't just go using them, now.
-s Start pvmd in slave mode. Hostfile cannot be used, five additional parameters must be supplied: master pvmd index, master IP, master MTU, slave pvmd index, and slave IP.
-S Same as -s, but slave pvmd doesn't wait for its stdin to be closed after printing its parameters. Used for manual startup.
-f Slave doesn't fork after configuration (useful if the slave is to be controlled or monitored by some process).
Lines beginning with a splat ( # ), optionally preceded by whitespace, are ignored.
A simple host file might look like:
# my first host file
thud
fred
wilma
barney
betty
This specifies the names of five hosts to be configured in the virtual machine.
The master pvmd for a group is started by hand on the localhost, and it starts slaves on each of the remaining hosts using the rsh or rexec command. The master host may appear on any line of the hostfile, but must have an entry.
The simple format above works fine if you have the same login name on all five machines and the name of the master host in your .rhosts files on the other four.
There are several host file options available:
bx=PATH Specifies the debugger program path. Note: the environment variable PVM_DEBUGGER can also be set.
Each of the flags above has a default value. These are:
* lo=afriend so=pw
This sets new default values for `lo' and `so' for the remainder of the host file, or until the next `*' line. Options set on the last `*' line also apply to hosts added dynamically using pvm_addhosts().
Host options can be set without starting the hosts automatically. Information on host file lines beginning with `&' is stored, but the hosts are not started until added using pvm_addhosts().
Example hostfile:
# hostfile for testing on various platforms fonebone
refuge
# installed in /usr/local/here
after typing the given command on host honk, you should see a line like: ddpro<2312> arch<ALPHA> ip<80a95c43:0a8e> mtu<4096>
type this line on the tty of the master pvmd. You should then see: Thanks
and the two pvmds should be able to communicate.
Note you can't start the master using the console or background it when using this option.
STOPPING PVMD3
The preferred method of stopping all the pvmds is to give the halt command in the PVM console. This kills all pvm tasks, all the remote daemons, the local daemon, and finally the console itself. If the master pvmd is killed manually it should be sent a SIGTERM signal to allow it to kill the remote pvmds and clean up various files.
The pvmd can be killed in a manner that leaves the file /tmp/pvmd.uid behind on one or more hosts. Uid is the numeric user ID (from /etc/passwd) of the user. This will prevent PVM from restarting on that host. Deletion of this file will fix this problem:
rm `( grep $user /etc/passwd || ypmatch $user passwd ) | awk -F: `{print "/tmp/pvmd."$3; exit}'`
SEE ALSO
pvm(1PVM),
pvm_intro(1PVM)