Re: [OMPI users] mpirun w/ enable-mpi-threads spinning up cputime when app path is invalid

Sorry - went to one of your links to get that info. We know OMPI 1.2.x isn't thread safe. This is unfortunately another example of it. Hopefully, 1.3 will be better. Ralph On 7/2/08 11:01 AM, "Ralph H Castain" wrote: > Out of curiosity - what version of OMPI are you using? >

Re: [OMPI users] mpirun w/ enable-mpi-threads spinning up cputime when app path is invalid

Out of curiosity - what version of OMPI are you using? On 7/2/08 10:46 AM, "Steve Johnson" wrote: > If mpirun is given an application that isn't in the PATH, then instead of > exiting it prints the error that it failed to find the executable and then > proceeds spins up cpu

[OMPI users] mpirun w/ enable-mpi-threads spinning up cputime when app path is invalid

If mpirun is given an application that isn't in the PATH, then instead of exiting it prints the error that it failed to find the executable and then proceeds spins up cpu time. strace shows an endless stream of sched_yield(). For example, if "blah" doesn't exist: mpirun -np 16 blah Ditto if