Typical practice would be to put a ./myprogram in there to avoid any possible confusion with a “myprogram” sitting in your $PATH. We should search the PATH to find your executable, but the issue might be that it isn’t your PATH on a remote node.
So the question is: are you launching strictly local? Or are you launching a job that spans multiple nodes? > On Jul 29, 2016, at 5:12 PM, Phil Regier <preg...@penguincomputing.com> wrote: > > I might be three steps behind you here, but does "mpirun <args> pwd" show > that all your launched processes are running in the same directory as the > mpirun command? I assume that "mpirun <args> env" would show that your PATH > variable is being passed along correctly, since you don't have any problems > with absolute paths. In any event, is PATH=$PWD/dir/bin not an option? > > Seems to me that this last would be good practice for location-sensitive > launches in general, though I do tend to miss things. > > On Fri, Jul 29, 2016 at 4:34 PM, Schneider, David A. > <david...@slac.stanford.edu <mailto:david...@slac.stanford.edu>> wrote: > I am finding, on linux, rhel7, with openmpi 1.8.8 and 1.10.3, that mpirun > won't find apps that are specified on a relative path, i.e, if I have > > PATH=dir/bin > > and I am in a directory which has dir/bin as a subdirectory, and an > executable bir/bin/myprogram, I can't do > > mpirun myprogram > > I get the error message that > > mpirun was unable to find the specified executable file, and therefore > did not launch the job. > > whereas if I put an absolute path, something like > > PATH=/home/me/dir/bin > > then it works. > > This causes some problematic silent failure, sometimes we use relative > directories to override a 'base' release, so if I had > > PATH=dir/bin:/central/install/dir/bin > > and myprogram was in both dir/bin and /central/install/dir/bin, through > mpirun, I would be running myprogram from the central install, but otherwise > I would run it from my own directory. > > Do other people find this is the case? I wonder if it is a problem that got > introduced through our installation of openmpi. We do create relocatable > rpm's, and I'm also trying openmpi from a conda package that is relocatable, > I think all the prefix paths in the binary and text files were corrected > properly for the install - at least everything else seems to work. > > best, > > David Schneider > SLAC/LCLS > _______________________________________________ > users mailing list > users@lists.open-mpi.org <mailto:users@lists.open-mpi.org> > https://rfd.newmexicoconsortium.org/mailman/listinfo/users > <https://rfd.newmexicoconsortium.org/mailman/listinfo/users> > > > > -- > Phil Regier, Professional Services Engineer > preg...@penguincomputing.com <mailto:preg...@penguincomputing.com> > 415.954.2864 (office) > 415.748.9056 (cell) > _______________________________________________ > users mailing list > users@lists.open-mpi.org > https://rfd.newmexicoconsortium.org/mailman/listinfo/users
_______________________________________________ users mailing list users@lists.open-mpi.org https://rfd.newmexicoconsortium.org/mailman/listinfo/users
