Thanks for your fix.
You say that the environment is only taken in
account during register. There is another variable set in the
environment in opal-restart.c. Does the following still work:
opal-restart.c:
(void) mca_base_var_env_name("crs", &tmp_env_var);
opal_setenv(tmp_env_var,
Good catch. Fixing now.
-Nathan
On Mon, Mar 17, 2014 at 02:50:02PM +0100, Adrian Reber wrote:
> On Fri, Mar 14, 2014 at 10:18:06PM +, Hjelm, Nathan T wrote:
> > The preferred way is to use mca_base_var_find and then call
> > mca_base_var_[set|get]_value. For performance sake we only look at
On Fri, Mar 14, 2014 at 10:18:06PM +, Hjelm, Nathan T wrote:
> The preferred way is to use mca_base_var_find and then call
> mca_base_var_[set|get]_value. For performance sake we only look at the
> environment when the variable is registered.
I believe I found a bug in mca_base_var_set_value
...@open-mpi.org
> Subject: [OMPI devel] usage of mca variables in orte-restart
>
> I am now trying to run orte-restart. As far as I understand it
> orte-restart analyzes the checkpoint metadata and then tries to exec()
> mpirun which then starts opal-restart. During the startup of
>
: devel [devel-boun...@open-mpi.org] on behalf of Adrian Reber
[adr...@lisas.de]
Sent: Friday, March 14, 2014 3:05 PM
To: de...@open-mpi.org
Subject: [OMPI devel] usage of mca variables in orte-restart
I am now trying to run orte-restart. As far as I understand it
orte-restart analyzes the checkpoint
I don't believe we support changing the value of an MCA param on-the-fly -
you'd need to transfer it to an appropriate-level global that you can change as
required
On Mar 14, 2014, at 2:05 PM, Adrian Reber wrote:
> I am now trying to run orte-restart. As far as I understand it
> orte-restart a
I am now trying to run orte-restart. As far as I understand it
orte-restart analyzes the checkpoint metadata and then tries to exec()
mpirun which then starts opal-restart. During the startup of
opal-restart (during initialize()) detection of the best CRS module is
disabled:
/*
* Turn of
