PMIX_INFO(1)

πŸ’– PMIX_INFO πŸ’–

okay bestie, so this is the PMIX_INFO(1) page from the OpenPMIx manual set β€” it's the little command that spills ALL the tea about your PMIx install. pull up a chair 🫢


✨ NAME ✨

pmix_info β€” the way that you can display literally everything about your PMIx installation. no cap.


🌸 SYNOPSIS 🌸

pmix_info [options]

πŸ¦‹ DESCRIPTION πŸ¦‹

so pmix_info gives you the full detailed rundown on your PMIx installation. it's giving detective energy πŸ” and it's genuinely useful for at least three (3) extremely common scenarios:

  1. checking your local configuration and seeing how PMIx was actually installed.
  2. submitting bug reports / help requests to the PMIx community (see Getting help <>).
  3. seeing a list of installed PMIx plugins and querying what MCA parameters they support.

πŸ’… OPTIONS πŸ’…

pmix_info accepts the following options:

  • -h | --help <arg0> β€” show the help message. if you don't pass the optional argument, you get a generalized help message, basically the same info as what's right here. if you DO pass an argument, you get a more detailed help message for that specific command line option. obsessed with the specificity πŸ’–
  • -v | --verbose β€” turn on debug output.
  • -V | --version β€” print the version and exit. bye πŸ‘‹
  • -a | --all β€” show all configuration options and MCA parameters.
  • --arch β€” show the architecture that PMIx was compiled on.
  • -c | --config β€” show configuration options
  • --hostname β€” show the hostname that PMIx was configured and built on.
  • --internal β€” show internal MCA parameters. ⚠️ these are not meant to be modified by users, bestie. look, don't touch.
  • --param <arg0>:<arg1>,<arg2> β€” show MCA parameters. the first parameter is the framework (or the keyword β€œall”); the second parameter is a comma-delimited list of specific component names. if only <arg0> is given, then all components will be reported. iykyk ✨
  • --path <type> β€” show the paths that PMIx was configured with. accepts the following parameters: prefix, bindir, libdir, incdir, pkglibdir, sysconfdir.
  • --pretty-print β€” when used in conjunction with other parameters, the output is displayed in β€œprettyprint” format (this is the default, so it's lowkey the main character 😌)
  • --parsable β€” when used in conjunction with other parameters, the output is displayed in a machine-parsable format.
  • --parseable β€” a synonym for --parsable. same vibe, different spelling πŸŽ€
  • --show-failed β€” show the components that failed to load, along with the reason why they failed. πŸ’€ rip to those components.
  • --selected-only β€” show only variables from selected components.

πŸ‘‘ EXIT STATUS πŸ‘‘

returns 0 if successful, non-zero if an error is encountered. that's it, that's the whole thing 🫢


🌈 EXAMPLES 🌈

examples of using this command, bestie. come thru:

show the default output of options and listing of installed components in a human-readable / prettyprint format:

pmix_info

show the default output of options and listing of installed components in a machine-parsable format:

pmix_info --parsable

show the MCA parameters of the β€œopa” PNET component in a human-readable / prettyprint format:

pmix_info --param pnet opa

show the bindir that PMIx was configured with:

pmix_info --path bindir

show the version of PMIx version numbers in a prettyprint format:

pmix_info --version

show all information about the PMIx installation, including all components that can be found, all the MCA parameters that they support, versions of PMIx and the components, etc.:

pmix_info --all

🧚 SEE ALSO 🧚

see also:

openpmix(5) <#man5-openpmix>


2014-2026, OpenPMIx Community


okay that's the whole page, bestie, you ate that πŸ“

this has been the OpenPMIx manual, page PMIX_INFO(1), dated Jan 22, 2026 β€” sending you so much love, now go run pmix_info --all and be iconic πŸ’…βœ¨

πŸ“¦ where this page comes from