Ah - now that is easily fixed, without breaking the support for everyone
else. I'll commit the fix right away.
Thanks
Ralph
On Mon, Jun 22, 2009 at 11:12 AM, Iain Bason wrote:
> Ralph Castain wrote:
>
>> Yes, but look at orte/mca/plm/rsh/plm_rsh_module.c:
>>
>> /* ensure that only the ssh
Ralph Castain wrote:
Yes, but look at orte/mca/plm/rsh/plm_rsh_module.c:
/* ensure that only the ssh plm is selected on the remote daemon */
var = mca_base_param_environ_variable("plm", NULL, NULL);
opal_setenv(var, "rsh", true, &env);
free(var);
This is done in "ssh_chi
Yes, but look at orte/mca/plm/rsh/plm_rsh_module.c:
/* ensure that only the ssh plm is selected on the remote daemon */
var = mca_base_param_environ_variable("plm", NULL, NULL);
opal_setenv(var, "rsh", true, &env);
free(var);
This is done in "ssh_child", right before we fork_exec
Ralph Castain wrote:
I'm sorry, but this change is incorrect.
If you look in orte/mca/ess/base/ess_base_std_orted.c, you will see
that -all- orteds, regardless of how they are launched, open and
select the PLM.
I believe you are mistaken. Look in plm_base_launch_support.c:
/* Th
I apologize - I had to revert this myself as it broke support for backend
launches on Torque and SLURM, which a number of us are actively using.
Please see the commit message for r21488 for a complete explanation.
Thanks
Ralph
On Fri, Jun 19, 2009 at 8:36 PM, Ralph Castain wrote:
> I'm sorry, b
I'm sorry, but this change is incorrect.
If you look in orte/mca/ess/base/ess_base_std_orted.c, you will see that
-all- orteds, regardless of how they are launched, open and select the PLM.
This change causes rsh launched daemons to
doubly-open/select the PLM, which is a very bad idea.
Would you
