- "Ralph Castain" wrote:
> Let me point out the obvious since this has plagued
> us at LANL with regard to this concept. If a user
> wants to do something different, all they have to
> do is download and build their own copy of OMPI.
One possibility may be to have OMPI
On Sep 5, 2009, at 3:00 AM, Jeff Squyres wrote:
On Sep 4, 2009, at 5:47 PM, Sylvain Jeaugey wrote:
Understood. So, let's say that we're only implementing a hurdle to
discourage users from doing things wrong. I guess the efficiency of
this
will reside in the message displayed to the user
On Sep 4, 2009, at 2:34 PM, Sylvain Jeaugey wrote:
hg -R "$srcdir" tip | head -1 | grep "^changeset:" | cut -d: -f3
Good catch; I changed it slightly from this to:
hg -v -R "$srcdir" tip | grep ^changeset: | head -n 1 | cut -d: -f3
I put this on the trunk since I couldn't push to your bb
...@open-mpi.org
> [mailto:devel-boun...@open-mpi.org] On Behalf Of Ralph Castain
> Sent: Friday, September 04, 2009 8:28 AM
> To: Open MPI Developers
> Subject: Re: [OMPI devel] RFC - "system-wide-only" MCA parameters
>
> Just want to make this very clear, since other LANL people
&g
Understood. So, let's say that we're only implementing a hurdle to
discourage users from doing things wrong. I guess the efficiency of this
will reside in the message displayed to the user ("You are about to break
the entire machine and you will be fined if you try to circumvent this in
any
Just want to make this very clear, since other LANL people are on this
list.
I am in no way saying that LANL users are ill-intentioned or
deliberately attempting to circumvent system restrictions. See my
other note for the most common scenarios that lead to this problem and
you will see
I fear you all misunderstood me. This isn't a case of sabotage or
nasty users, but simply people who do something that they don't
realize can cause a problem.
Our example is quite simple. We have IB network for MPI messages, and
several Ethernet NICs that are dedicated to system-level
On Fri, 2009-09-04 at 07:50 -0600, Ralph Castain wrote:
> Let me point out the obvious since this has plagued us at LANL with
> regard to this concept. If a user wants to do something different, all
> they have to do is download and build their own copy of OMPI.
>
> Amazingly enough, that is
Looks like users at LANL are not very nice ;)
Indeed, this is no hard security. Only a way to prevent users from doing
mistakes. We often give users special tuning for their application and
when they see their application is going faster, they start messing with
every parameter hoping that it
Hi,
Ralph Castain wrote:
Let me point out the obvious since this has plagued us at LANL with
regard to this concept. If a user wants to do something different, all
they have to do is download and build their own copy of OMPI.
We are well aware of that. It is relatively easy for a user to
Let me point out the obvious since this has plagued us at LANL with
regard to this concept. If a user wants to do something different, all
they have to do is download and build their own copy of OMPI.
Amazingly enough, that is exactly what they do. When we build our
production versions, we
On Fri, 2009-09-04 at 13:55 +0200, Sylvain Jeaugey wrote:
> On Fri, 4 Sep 2009, Jeff Squyres wrote:
>
> > I haven't looked at the code deeply, so forgive me if I'm parsing this
> > wrong:
> > is the code actually reading the file into one list and then moving the
> > values to another list?
On Fri, 2009-09-04 at 13:34 +0200, Sylvain Jeaugey wrote:
> On Fri, 4 Sep 2009, Jeff Squyres wrote:
>
> > --
> > *** Checking versions
> > checking for SVN version... done
> > checking Open MPI version... 1.4a1hgf11244ed72b5
> > up to changeset c4b117c5439b
> > checking Open MPI release
On Fri, 4 Sep 2009, Jeff Squyres wrote:
I haven't looked at the code deeply, so forgive me if I'm parsing this wrong:
is the code actually reading the file into one list and then moving the
values to another list? If so, that seems a little hackish. Can't it just
read directly to the target
On Fri, 4 Sep 2009, Jeff Squyres wrote:
--
*** Checking versions
checking for SVN version... done
checking Open MPI version... 1.4a1hgf11244ed72b5
up to changeset c4b117c5439b
checking Open MPI release date... Unreleased developer copy
checking Open MPI Subversion repository version...
On Fri, 2009-09-04 at 10:05 +0300, Jeff Squyres wrote:
> On Sep 3, 2009, at 12:23 PM, Nadia Derbey wrote:
>
> > What: Define a way for the system administrator to prevent users from
> > overwriting the default system-wide MCA parameters settings.
> >
>
> In general, I think this is great
On Sep 3, 2009, at 12:23 PM, Nadia Derbey wrote:
What: Define a way for the system administrator to prevent users from
overwriting the default system-wide MCA parameters settings.
In general, I think this is great stuff. I have a few nit picks.
(BTW: you might want to run
On Sep 4, 2009, at 8:26 AM, Nadia Derbey wrote:
> Can the file name ( openmpi-priv-mca-params.conf ) also be
configurable ?
No, it isn't, presently, but this can be changed if needed.
If it's configurable, it must be configurable at configure time -- not
run time -- otherwise, a user
On Thu, 2009-09-03 at 19:29 -0400, Graham, Richard L. wrote:
> What happens if $sysconfdir/openmpi-priv-mca-params.conf is missing ?
If it is missing, everything works as today: any parameter declared in
$sysconfdir/openmpi-mca-params.conf is considered as system-wide and can
be overwritten as
What happens if $sysconfdir/openmpi-priv-mca-params.conf is missing ?
Can the file name ( openmpi-priv-mca-params.conf ) also be configurable ?
Rich
On 9/3/09 5:23 AM, "Nadia Derbey" wrote:
What: Define a way for the system administrator to prevent users from
20 matches
Mail list logo