Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mca_param_files format documentation questions #161

Open
apjanke opened this issue Dec 11, 2018 · 0 comments
Open

mca_param_files format documentation questions #161

apjanke opened this issue Dec 11, 2018 · 0 comments

Comments

@apjanke
Copy link
Contributor

apjanke commented Dec 11, 2018

Over in the FAQ Tuning section, it says:

By default, two files are searched (in order):

  1. $HOME/.openmpi/mca-params.conf: The user-supplied set of values takes the highest precedence.
  2. $prefix/etc/openmpi-mca-params.conf: The system-supplied set of values has a lower precedence.
    More specifically, the MCA parameter mca_param_files specifies a colon-delimited path of files to search for MCA parameters. Files to the left have lower precedence; files to the right are higher precedence.

But with Open MPI 4.0.0, when I query mca_param_files with ompi_info, I get:

$ ompi_info --param all all --level 9 | grep -i mca_base_param_files
            MCA mca base: parameter "mca_param_files" (current value: "/Users/janke/.openmpi/mca-params.conf,/usr/local/Cellar/open-mpi/4.0.0/etc/openmpi-mca-params.conf", data source: default, level: 2 user/detail, type: string, deprecated, synonym of: mca_base_param_files)
            MCA mca base: parameter "mca_base_param_files" (current value: "/Users/janke/.openmpi/mca-params.conf,/usr/local/Cellar/open-mpi/4.0.0/etc/openmpi-mca-params.conf", data source: default, level: 2 user/detail, type: string, synonyms: mca_param_files)

This seems inconsistent with that FAQ documentation in two ways:

  • It's a comma-separated list, not a colon-separated list.
  • The higher-precedence file seems to appear on the left, not the right.

Am I misinterpreting the documentation here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant