Hello everybody,
we are seeing the sypmptoms described in
https://github.com/open-mpi/ompi/issues/11557
However, according to the systems package manager (dnf) all munge
related packages on the build node and the execution node are identical,
see details at the bottom. So, the explanation given b
Hello again,
I should add that the openmpi configure decides to use the internal pmix
configure: WARNING: discovered external PMIx version is less than internal
version 3.x
configure: WARNING: using internal PMIx
...
...
checking if user requested PMI support.
v2.2.0, Component
v4.1.5)
MCA topo: treematch (MCA v2.1.0, API v2.2.0, Component
v4.1.5)
MCA vprotocol: pessimist (MCA v2.1.0, API v2.0.0, Component
v4.1.5)
>
> Z. Matthias Kraw
" != "internal" && (test -z
> "$with_pmix" || test "$with_pmix" = "yes")
>
> then :
>
> if test "$opal_external_pmix_version" != "3x"
>
>
> and replace the last line with
>
> if te
Hello,
>
> Hi,
>
> I am using OpenMPI 4.1.1 (without a scheduler) and I want to limit the
> number of CPU or threads a specific user (or host, if I must) can use.
> Is there a configuration or environment variable I can use? This user
> has not been following our resource management policy so
