openmpi

* Additionally, fixes the `NULL` option to `OMPI_MCA_plm_rsh_agent`
   would would also lead to a segv. Now it operates as intended by
   disqualifying the `rsh` component and falling back onto the `isolated`
   component.

Signed-off-by: Joshua Hursey <jhursey@us.ibm.com>
(cherry picked from commit 62d0058738e8a111cd099199bc5f1886f13aa8ec)

2020-01-27 10:34:28 -06:00

configure.m4

m4: rename OMPI_SUMMARY_* macros to OPAL_SUMMARY_*

2016-04-20 08:40:00 -07:00

help-plm-rsh.txt

Now that we have an "isolated" PLM component, we cannot just let rsh silently decline to run when it cannot find a launch agent - if we do, then we will -always- run on the local node. So if the user specifies a launch agent and we can't find it, then generate a pretty error message, report a fatal error back to the component select, and exit out.

2015-09-24 07:16:48 -07:00

Makefile.am

mca: Dynamic components link against project lib

2017-08-24 11:56:16 -04:00

owner.txt

add owner files to opa/ompi/orte mca directories