21.1.3. prted
prted — PRRTE daemon
21.1.3.1. SYNOPSIS
prted [options]
21.1.3.2. DESCRIPTION
prted is the per-node daemon of a PMIx Reference Runtime
Environment (PRRTE) distributed virtual machine (DVM). One prted
runs on each node of the DVM other than the one hosting the DVM
controller; it launches and monitors the application processes on its
node, serves as their local PMIx server, and relays their I/O and
status to the controller.
Users do not normally run prted themselves: the DVM controller
(prte(1) or prterun(1))
starts it on each remote node, through the launcher appropriate to the
environment, and passes it the options it needs. The options below are
documented chiefly for those debugging a DVM’s startup, or setting one
up by hand.
prted --help <option> prints the full description of an option.
21.1.3.3. OPTIONS
General options
21.1.3.3.1. -h | --help [<option>]
Print the list of options, or the full help for the named option.
21.1.3.3.2. -v | --verbose
Enable typical debug options.
21.1.3.3.3. -V | --version
Print version and exit.
Debug options
21.1.3.3.4. --debug-daemons
Debug daemon output enabled. This is a somewhat limited stream of information normally used to simply confirm that the daemons started. Includes leaving the output streams open.
21.1.3.3.5. --debug-daemons-file
Debug daemon output is enabled and all output from the daemons is redirected into files with names of the form:
output-prted-<daemon-nspace>-<nodename>.log
These names avoid conflict on shared file systems. The files are located in the top-level session directory assigned to the DVM.
See the “Session directory” HTML documentation for additional details about the PRRTE session directory.
21.1.3.3.6. --leave-session-attached
Do not discard stdout/stderr of remote PRRTE daemons. The primary use for this option is to ensure that the daemon output streams (i.e., stdout and stderr) remain open after launch, thus allowing the user to see any daemon-generated error messages. Otherwise, the daemon will “daemonize” itself upon launch, thereby closing its output streams.
DVM options
21.1.3.3.7. --prtemca <key> <value>
Pass a PRRTE MCA parameter.
Syntax: --prtemca <key> <value>, where key is the parameter
name and value is the parameter value.
21.1.3.3.8. --pmixmca <key> <value>
Pass a PMIx MCA parameter
Syntax: --pmixmca <key> <value>, where key is the parameter
name and value is the parameter value.
21.1.3.3.9. --dvm-master-uri <uri>
Specify the URI of the DVM master, or the name of the file (specified
as file:filename) that contains that info.
21.1.3.3.10. --parent-uri <uri>
Specify the URI of the prted acting as the parent of this prted in a tree-based spawn operation.
21.1.3.3.11. --tree-spawn
A tree-based spawn operation is in progress.
21.1.3.3.12. --bootstrap
Self-construct the DVM based on a configuration file.
21.1.3.3.13. --uniform-nodes
The uniform-nodes command line directive is used to indicate that
the allocated nodes should be treated as having only one topology, so
optimize the launch for that scenario. This includes ensuring that all
CPU allocations are the same on each node, that each node contains the
same number of devices and topological layers, etc.
Note
The runtime does not currently support mixes of chips with different endianness.
Specific options
21.1.3.3.14. --daemonize
Daemonize this prted into the background, detaching it from the
terminal that started it and closing its output streams. This is what
the DVM controller normally directs a remotely-launched daemon to do;
see --leave-session-attached for the way to keep those streams open
instead.
21.1.3.3.15. --set-sid
Direct the daemon to separate from the current session.
21.1.3.3.16. --system-server
Start the daemon as the system server on its node.
21.1.3.3.17. --pubsub-server <uri>
Contact information for external PRRTE publish/lookup data server.
21.1.3.3.18. --allow-run-as-root
Allow execution as root (STRONGLY DISCOURAGED).
Running as root exposes the user to potentially catastrophic file system corruption and damage — e.g., if the user accidentally points the root of the session directory to a system required point, this directory and all underlying elements will be deleted upon job completion, thereby rendering the system inoperable.
It is recognized that some environments (e.g., containers) may require operation as root, and that the user accepts the risks in those scenarios. Accordingly, one can override PRRTE’s run-as-root protection by providing one of the following:
The
--allow-run-as-rootcommand line directiveAdding BOTH of the following environmental parameters:
PRTE_ALLOW_RUN_AS_ROOT=1PRTE_ALLOW_RUN_AS_ROOT_CONFIRM=1
Again, we recommend this only be done if absolutely necessary.
21.1.3.4. DEPRECATED COMMAND LINE OPTIONS
--hetero-nodesHas no effect beyond a warning: heterogeneous nodes are detected automatically. Give
--uniform-nodesif the nodes are known to be identical.--debugHas no effect; it is accepted, with a warning, so that old command lines still parse.
See also