Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [OMPI users] mpirun w/ enable-mpi-threads spinning up cputime when app path is invalid
From: Ralph H Castain (rhc_at_[hidden])
Date: 2008-07-02 13:01:38

Out of curiosity - what version of OMPI are you using?

On 7/2/08 10:46 AM, "Steve Johnson" <steve_at_[hidden]> 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 time. strace shows an endless stream of sched_yield().
> For example, if "blah" doesn't exist:
> mpirun -np 16 blah
> Ditto if ./blah doesn't exist and mpirun is called as
> mpirun -np 16 ./blah
> OS: CentOS 5.1
> Kernel:
> Arch: x86_64
> glibc/pthread: glibc-2.5-18.el5_1.1
> GCC: 4.1.2-14.el5
> CC=gcc
> CXX=g++
> F77=gfortran
> FC=gfortran
> ./configure --with-tm --prefix=$HOME/openmpi --libdir=$HOME/openmpi/lib64
> --enable-mpi-threads
> A qsig -s 15 will terminate the mpirun processes.
> ompi_info is at
> is at
> Also confirmed this on openSUSE 10.2,, x86_64,
> glibc-2.5-34.7, gcc-4.1.3-29.
> // Steve
> _______________________________________________
> users mailing list
> users_at_[hidden]