No, it isn't - but we aren't really maintaining the 1.6 series any more. You might try updating to 1.6.5 and see if it remains there
On Aug 29, 2014, at 9:12 AM, Maxime Boissonneault <maxime.boissonnea...@calculquebec.ca> wrote: > It looks like > -npersocket 1 > > cannot be used alone. If I do > mpiexec -npernode 2 -npersocket 1 ls -la > > then I get no error message. > > Is this expected behavior ? > > Maxime > > > Le 2014-08-29 11:53, Maxime Boissonneault a écrit : >> Hi, >> I am having a weird error with OpenMPI 1.6.3. I run a non-MPI command just >> to exclude any code error. Here is the error I get (I run with set -x to get >> the exact command that are run). >> >> ++ mpiexec -npersocket 1 ls -la >> -------------------------------------------------------------------------- >> The requested stdin target is out of range for this job - it points >> to a process rank that is greater than the number of processes in the >> job. >> >> Specified target: 0 >> Number of procs: 0 >> >> This could be caused by specifying a negative number for the stdin >> target, or by mistyping the desired rank. Remember that MPI ranks begin >> with 0, not 1. >> >> Please correct the cmd line and try again. >> >> How can I debug that ? >> >> Thanks, >> > > > -- > --------------------------------- > Maxime Boissonneault > Analyste de calcul - Calcul Québec, Université Laval > Ph. D. en physique > > _______________________________________________ > users mailing list > us...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users > Link to this post: > http://www.open-mpi.org/community/lists/users/2014/08/25190.php
