# -*- text -*-
#
# Copyright (c) 2004-2006 The Trustees of Indiana University and Indiana
#                         University Research and Technology
#                         Corporation.  All rights reserved.
# Copyright (c) 2004-2006 The University of Tennessee and The University
#                         of Tennessee Research Foundation.  All rights
#                         reserved.
# Copyright (c) 2004-2005 High Performance Computing Center Stuttgart,
#                         University of Stuttgart.  All rights reserved.
# Copyright (c) 2004-2005 The Regents of the University of California.
#                         All rights reserved.
# Copyright (c) 2014-2020 Intel, Inc.  All rights reserved.
# Copyright (c) 2015-2020 Cisco Systems, Inc.  All rights reserved
# Copyright (c) 2021-2026 Nanook Consulting  All rights reserved.
# $COPYRIGHT$
#
# Additional copyrights may follow
#
# $HEADER$
#
#
[include-exclude]
Both TCP interface include and exclude lists were specified:

  Include: %s
  Exclude: %s

Only one of these can be given.
#
[not-parseable]
The specified network is not parseable. Since we cannot determine
your desired intent, we cannot establish a TCP socket for PMIx
communications and will therefore abort. Please correct the network
specification and retry.
#
[invalid if_inexclude]
WARNING: An invalid value was given for pmix_ptl_base_if_%s.  This
value will be ignored.

  Local host: %s
  Value:      %s
  Message:    %s
#
[accept failed]
WARNING: The accept(3) system call failed on a TCP socket.  While this
should generally never happen on a well-configured HPC system, the
most common causes when it does occur are:

  * The process ran out of file descriptors
  * The operating system ran out of file descriptors
  * The operating system ran out of memory

Your job may hang until the failure reason is fixed
(e.g., more file descriptors and/or memory becomes available), and may
eventually timeout / abort.

  Local host:     %s
  Errno:          %d (%s)
  Probable cause: %s
#
[too-many-conns]
PMIx has found multiple possible servers to which it could
connect. Further guidance is required to ensure the connection
is made to a desirable server. Guidance can be in the form
of the namespace or PID of a specific server, a directive to
connect to a system server, a specific URI to use, or the name
of a rendezvous file.

Some connection handles have been read from files named pmix.*
in subdirectories of $TMPDIR; delete them if they are stale.
#
[file-not-found]
There was an error when attempting to access the specified server
rendezvous file:

  Filename:  %s
  Error:     %s

Please correct the error and try again.
#
[mismatch-id]
The %s ID of the client process does not match the ID registered
by the host runtime:

  Process:     %u
  Registered:  %u

This could be a security issue. Please check the situation and
try again.
#
[no-remote-interfaces]
You requested support for remote tool connections, but no non-loopback
interfaces were found after applying any include or exclude directives:

  Include:    %s
  Exclude:    %s
  Available:  %s

Please adjust your include or exclude to allow selection of a
non-loopback interface.
#
[no-loopback-interfaces]
You requested support for only local tool connections, but no loopback
interfaces were found after applying any include or exclude directives:

  Include:    %s
  Exclude:    %s
  Available:  %s

Please adjust your include or exclude to allow selection of a
loopback interface.
#
[no-available-interfaces]
You requested support for tool connections, but no available
interfaces were found after applying any include or exclude directives:

  Include:    %s
  Exclude:    %s
  Available:  %s

Please adjust your include or exclude to allow selection of an
available interface.
#
[unexpected-message]
The PMIx messaging system has received an unexpected message:

  Peer: %s
  Tag:  %u

The message cannot be processed and will be ignored. Please
report this error to the PMIx developers.
