Terry,
Linux Slackware, quite outdated kernel 2.6.15, gcc 3.4.6,
Yes, that was slightly oversubscribed - just to perform sanity tests
locally. Obviously, I changed that part and I send data in bigger chunks
(I think that should work faster anyway), also on not oversubscribed
cluster machine th
Hello,
I have installed openmpi from the ubuntu repository for the 64-bit
dual core AMD processor.
and i tried to compile the simple test program with the help of the
tutorial page but nothing seems to happen.
#include
#include
int main(int argc,char *argv[])
{
int rank;
MPI_
Dont use the name 'test' test is a unix command and it causes
problems when you name things 'test'
If you try
mpirun -np 4 ./test
it will work because that will use the test you just created not the
regular 'test'
But really dont use the name test and it will work as expected.
Brock Palen
Jeff, you were right. I did a series of Spawns and consecutive Merges
and forgot to set the exception handler with the newly created
intra-communicators. Since these properties obviously are not inherited
(which would be kind of hard considering that there are multiple
communicators to be merged),
Hello Brock,
I renamed the whole file as mpitest1.c and issued the following command
mpicc mpitest1.c -o mpitest1
mpirun -np 4 ./mpitest1
then i got the following output:
--
Sorry! You were supposed to get help about:
The real error message hidden behind the argv0-not-accesible is:
Failed to find or execute the following executable:
george.
On Nov 14, 2007, at 4:08 PM, Sajjad wrote:
Hello Brock,
I renamed the whole file as mpitest1.c and issued the following
command
mpicc mpitest1.c -o mpitest1
mpi
What version of Open MPI are you using? I see that particular error
listed in the "rmgr" part of the code base, not the "pls" part of the
code base in the current release (1.2.4). Meaning: I'm guessing that
the fact that this help message is not found in your version has been
fixed in a l
Hi,
I am using openmpi 1.2.3 under ia64 machine. I typed "mpirun -d --tmpdir
/home/565/kxc565/tmpdir -mca btl sm -np 400 ./testprogram". I found only
the first process can use my parameter setting to store tmp file, but
the second process used its default setting to store tmp file in /tmp
dir
