On Nov 1, 2008, at 7:39 AM, Jeff Squyres wrote:
On Oct 31, 2008, at 4:52 PM, Gilbert Grosdidier wrote:
To monitor the environment from inside the application, it could be
useful to
issue a 'system("printenv")' call at the very beginning of the main
program,
even before (and after, btw) the MPI
On Oct 31, 2008, at 4:52 PM, Gilbert Grosdidier wrote:
To monitor the environment from inside the application, it could be
useful to
issue a 'system("printenv")' call at the very beginning of the main
program,
even before (and after, btw) the MPI_Init call, when running in
serial job mode
Where did you put the environment variable related to MCF licence file and
MCF share libraries?
What is your default shell?
Did you test indicate the following?
Suppose you have 4 nodes,
on node 1, " mpirun -np 4 --host node1,node2,node3,node4 hostname" works,
but "mpirun -np4 --host node1,no
Hi,
To monitor the environment from inside the application, it could be useful to
issue a 'system("printenv")' call at the very beginning of the main program,
even before (and after, btw) the MPI_Init call, when running in serial job mode
with a single CAB, using mpirun.
HTH, Gilb
Hello,
I'm having problems using Open MPI on a cluster of Mercury Computer's
Cell Accelerator Boards (CABs).
We have an MPI application that is running on multiple CABs. The
application uses Mercury's MultiCore Framework (MCF) to use the Cell's
SPEs. Here's the basic problem. I can log
