Just to be specific, here is how we handle the orte_launch_agent in
rsh that makes it work:
/* now get the orted cmd - as specified by user - into our tmp
array.
* The function returns the location where the actual orted
command is
* located - usually in the final spot, but s
I believe you are using a bad example here George. If you look closely
at the code, you will see that we treat the orte_launch_agent
separately from everything else - it gets passed through the following
code:
int orte_plm_base_setup_orted_cmd(int *argc, char ***argv)
{
int i, loc;
Just for the sake of it. A funy command line to try:
[bosilca@dancer ~]$ mpirun --mca routed_base_verbose 0 --leave-session-
attached -np 1 --mca orte_launch_agent "orted --mca
routed_base_verbose 1" uptime
[node03:22355] [[14661,0],1] routed_linear: init routes for daemon job
[14661,0]
On Jun 24, 2009, at 17:41 , Jeff Squyres wrote:
-
[14:38] svbu-mpi:~/svn/ompi/orte % mpirun --mca plm_base_verbose 100
--leave-session-attached -np 1 --mca orte_launch_agent "$bogus/bin/
orted -s" uptime
...lots of output...
srun --nodes=1 --ntasks=1 --kill-on-bad-exit --nodelist=svbu-
Hmm. Doesn't seem to work for me...
First, without the quotes -- a single argument ($bogus is the tree
where my OMPI is installed):
-
[14:36] svbu-mpi:~/svn/ompi/orte % mpirun --mca plm_base_verbose 100 --
leave-session-attached -np 1 --mca orte_launch_agent $bogus/bin/orted
uptime
.
If you read the original comment, we had concluded that there were no
multi-word options that were being passed back to the orteds. All
multi-word options known to us at that time, and still today, -only-
apply to the HNP. Hence, dropping them has zero impact.
To update you on the history:
I can't guarantee this for all PLM but I can confirm that rsh and
slurm (1.3.12) works well with this.
We try with and without Open MPI, and the outcome is the same.
[bosilca@dancer c]$ srun -n 4 echo "1 2 3 4 5 it works"
1 2 3 4 5 it works
1 2 3 4 5 it works
1 2 3 4 5 it works
1 2 3 4 5 it wo
The problem is that they don't get there properly. We have been
through this debate multiple times for several years - every so often,
someone decides to try this again.
The problem is that the mca param that reaches the other end has
quotes around it in some environments, and doesn't in ot
Then I guess you will be happy to learn that instead of eating your
multi word arguments we now pass them to your srun as expected.
george.
On Jun 24, 2009, at 16:18 , Jeff Squyres wrote:
As a non-rsh'er (I run all my jobs in SLURM), this is very important
to me.
Please revert.
On Ju
As a non-rsh'er (I run all my jobs in SLURM), this is very important
to me.
Please revert.
On Jun 24, 2009, at 4:15 PM, Ralph Castain wrote:
Yo George
This commit is going to break non-rsh launchers. While it is true
that the rsh launcher may handle multi-word options by putting them
Yo George
This commit is going to break non-rsh launchers. While it is true that the
rsh launcher may handle multi-word options by putting them in quotes, we
specifically avoided it here because it breaks SLURM, Torque, and others.
This is why we specifically put the inclusion of multi-word optio
11 matches
Mail list logo
