Joshua Hursey 4c1160e257 Fix tree spawn routed component issue ... * Fix #6618 - See comments on Issue #6618 for finer details. * The `plm/rsh` component uses the highest priority `routed` component to construct the launch tree. The remote orted's will activate all available `routed` components when updating routes. This allows the opportunity for the parent vpid on the remote `orted` to not match that which was expected in the tree launch. The result is that the remote orted tries to contact their parent with the wrong contact information and orted wireup will fail. * This fix forces the orteds to use the same `routed` component as the HNP used when contructing the tree, if tree launch is enabled. Signed-off-by: Joshua Hursey <jhursey@us.ibm.com>		2019-08-29 16:26:43 -04: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	2015-02-22 15:10:23 -07:00
plm_rsh_component.c	Fix plm/rsh runtime check	2017-02-13 16:54:03 -08:00
plm_rsh_module.c	Fix tree spawn routed component issue	2019-08-29 16:26:43 -04:00
plm_rsh.h	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