1prte(1)                              PRRTE                             prte(1)
2
3
4

NAME

6       prte - Establish a PRTE Distributed Virtual Machine (DVM).
7

SYNOPSIS

9              prte [ options ]
10
11       Invoking prte via an absolute path name is equivalent to specifying the
12       --prefix option with a <dir> value equivalent to  the  directory  where
13       prte resides, minus its last subdirectory.  For example:
14
15              $ /usr/local/bin/prte ...
16
17       is equivalent to
18
19              $ prte --prefix /usr/local ...
20

QUICK SUMMARY

22       prte will establish a DVM that can be used to execute subsequent appli‐
23       cations.  Use of prte can be advantageous, for example, when  you  want
24       to  execute  a  number  of  short-lived tasks (e.g., in a workflow sce‐
25       nario).  In such cases, the time required to start the PRTE DVM can  be
26       a  significant fraction of the time to execute the overall application.
27       Thus, creating a persistent PRTE DVM can speed the  overall  execution.
28       In addition, a persistent PRTE DVM will support executing multiple par‐
29       allel applications while maintaining separation between  their  respec‐
30       tive cores.
31

OPTIONS

33       This  section  includes many commonly used options.  There may be other
34       options listed with prte --help.
35
36       -h, --help
37              Display help for this command
38
39       -V, --version
40              Print version number.  If no other  arguments  are  given,  this
41              will also cause prte to exit.
42
43       --daemonize
44              Daemonize the DVM daemons into the background
45
46       --no-ready-msg
47              Do not print a DVM ready message
48
49       --report-pid <arg0>
50              Print  out prte’s PID during startup.  The <arg0> must be a - to
51              indicate that the PID is to be output to stdout, a + to indicate
52              that  the  PID is to be output to stderr, or a filename to which
53              the PID is to be written.
54
55       --report-uri <arg0>
56              Print out prte’s URI during startup.  The <arg0> must be a -  to
57              indicate that the URI is to be output to stdout, a + to indicate
58              that the URI is to be output to stderr, or a filename  to  which
59              the URI is to be written.
60
61       --system-server
62              Start the DVM as the system server
63
64       --prefix <dir>
65              Prefix  directory  that  will be used to set the PATH and LD_LI‐
66              BRARY_PATH on the remote node before invoking the PRTE daemon.
67
68       Use one of the following options to specify which hosts (nodes) of  the
69       cluster to use for the DVM.  See prte-map(1) for more details.
70
71       -H, --host <host1,host2,...,hostN>
72              List of hosts for the DVM.
73
74       --hostfile <hostfile>
75              Provide a hostfile to use.
76
77       --machinefile <machinefile>
78              Synonym for -hostfile.
79
80       Setting MCA parameters:
81
82       --gpmixmca <key> <value>
83              Pass  global  PMIx MCA parameters that are applicable to all ap‐
84              plication contexts.  <key> is the parameter name; <value> is the
85              parameter value.
86
87       --mca <key> <value>
88              Send  arguments  to various MCA modules.  See the “MCA” section,
89              below.
90
91       --pmixmca <key> <value>
92              Send arguments to various PMIx MCA modules.  See the “MCA”  sec‐
93              tion, below.
94
95       --prtemca <key> <value>
96              Send  arguments to various PRTE MCA modules.  See the “MCA” sec‐
97              tion, below.
98
99       --pmixam <arg0>
100              Aggregate PMIx MCA parameter set file list.  The  arg0  argument
101              is a comma-separated list of tuning files.  Each file containing
102              MCA parameter sets for this application context.
103
104       The following options are useful for developers; they are not generally
105       useful to most PRTE users:
106
107       -d, --debug-devel
108              Enable debugging of the PRTE layer.
109
110       --debug-daemons-file
111              Enable  debugging of the PRTE daemons in the DVM, storing output
112              in files.
113

DESCRIPTION

115       prte starts a Distributed Virtual Machine (DVM) by launching  a  daemon
116       on  each node of the allocation, as modified or specified by the --host
117       and --hostfile options (See prte-map(1) for  more  details).   Applica‐
118       tions can subsequently be executed using the prun command.  The DVM re‐
119       mains in operation until receiving the pterm command.
120
121       When starting the Distributed Virtual Machine (DVM), prte  will  prefer
122       to  use the process starter provided by a supported resource manager to
123       start the prted daemons on the allocated compute nodes.  If a supported
124       resource  manager  or  process starter is not available then rsh or ssh
125       are used with a corresponding hostfile, or if no hostfile  is  provided
126       then all X copies are run on the localhost.
127

RETURN VALUE

129       prte  returns 0 if no abnormal daemon failure occurs during the life of
130       the DVM, and non-zero otherwise.
131
132
133
1342021-08-23                                                             prte(1)