Jeff Squyres 48c650c47a configury: minor updates to config summary output

2016-03-10 13:02:52 -08:00

..

configure.m4

configury: minor updates to config summary output

2016-03-10 13:02:52 -08: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