On Feb 22, 2014, at 10:14 AM, Suraj Prabhakaran
wrote:
>> Yeah, we added those capabilities specifically for this purpose. Indeed,
>> another researcher added this to Torque a couple of years ago, though it
>> didn't get pushed upstream. Also was added to Slurm.
>
> Thanks for your help . By
On a Scientific Linux 5.5 system the nightly snapshot
openmpi-1.7.5a1r30797 fails to build with following errors:
Making all in romio
make[3]: Entering directory
`/tmp/adrian/openmpi-compile/openmpi-1.7.5a1r30797/build/ompi/mca/io/romio/romio'
make[4]: Entering directory
`/tmp/adrian/openmpi-co
> Yeah, we added those capabilities specifically for this purpose. Indeed,
> another researcher added this to Torque a couple of years ago, though it
> didn't get pushed upstream. Also was added to Slurm.
Thanks for your help . By any chance you have more info on that one? Or a faint
idea where
On Feb 22, 2014, at 9:30 AM, Suraj Prabhakaran
wrote:
> Thanks Ralph.
>
> I cannot get rid of Torque since I am actually working on dynamic allocation
> of nodes for a running job on Torque. What I actually want to do is spawn
> processes on the dynamically assigned nodes since that is the m
Thanks Ralph.
I cannot get rid of Torque since I am actually working on dynamic allocation of
nodes for a running job on Torque. What I actually want to do is spawn
processes on the dynamically assigned nodes since that is the most easiest way
to expand MPI processes when a resource allocation
On Feb 21, 2014, at 5:55 PM, Suraj Prabhakaran
wrote:
> Hmm.. but in actual the MPI_Comm_spawn of parents and MPI_Init of children
> never returned!
Understood - my point was that the output shows no errors or issues. For some
reason, the progress thread appears to just stop. This usually in
