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.
It looks like I did not add the prefix path to the binary name before
fork/exec in orte-restart.
There is a string variable that you can use to get the appropriate prefix:
It's the same one that Ralph mentioned that orterun uses.
If you add that on there then you should be ok. You might want to check the
app-files produces use the prefix as well when referencing opal-restart.
On Wed, Mar 12, 2014 at 11:34 AM, Ralph Castain <rhc_at_[hidden]> wrote:
> That's what the --enable-orterun-prefix-by-default configure option is for
> On Mar 12, 2014, at 9:28 AM, Adrian Reber <adrian_at_[hidden]> wrote:
> > I am using orte-restart without setting my PATH to my Open MPI
> > installation. I am running /full/path/to/orte-restart and orte-restart
> > tries to run mpirun to restart the process. This fails on my system
> > because I do not have any mpirun in my PATH. Is it expected for an Open
> > MPI installation to set up the PATH variable or should it work using the
> > absolute path to the binaries?
> > Should I just set my PATH correctly and be done with it or should
> > orte-restart figure out the full path to its accompanying mpirun and
> > start mpirun with the full path?
> > Adrian
> > _______________________________________________
> > devel mailing list
> > devel_at_[hidden]
> > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> > Link to this post:
> devel mailing list
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
Assistant Professor of Computer Science
University of Wisconsin-La Crosse