On Sep 9, 2014, at 1:42 PM, Mike Dubman wrote:
> maybe we should have another MCA parameter to specify desired policy?
> LAST,CONCAT,FIRST and let user select it?
>
> basically, it is to mimic "setenv(var,val,overwrite)" behavior which is easy
> to explain and good to have.
Is there a use cas
I can't see how a user would know how to use such a thing - which mca params
can absorb a concatenated value? Why would you take the last vs the first
instead of just providing a value only once?
On Sep 9, 2014, at 10:42 AM, Mike Dubman wrote:
> maybe we should have another MCA parameter to s
maybe we should have another MCA parameter to specify desired policy?
LAST,CONCAT,FIRST and let user select it?
basically, it is to mimic "setenv(var,val,overwrite)" behavior which is
easy to explain and good to have.
On Tue, Sep 9, 2014 at 7:31 PM, Ralph Castain wrote:
> WHAT: Generate an
WHAT: Generate an error if the user provides duplicate MCA params on the
cmd line
WHY: User confusion due to unexpected behavior
WHEN: Tues, Sept 16 as this is a gating issue for 1.8.3 release
In the beginning, OMPI would look at a cmd line for MCA params - if a param was
listed
