Ralph Castain 0140ff048d 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. ... This required modifying the mca_component_select function to actually check the return code on a component query - it was blissfully ignoring it. Also do a little cleanup to avoid bombarding the user with multiple error messages. Thanks to Patrick Begou for reporting the problem		2015-09-24 07:16:48 -07:00
..
configure.m4	Purge whitespace from the repo	2015-06-23 20:59:57 -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	Purge whitespace from the repo	2015-06-23 20:59:57 -07:00
owner.txt	add owner files to opa/ompi/orte mca directories	2015-02-22 15:10:23 -07:00
plm_rsh_component.c	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
plm_rsh_module.c	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
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