1
1
openmpi/ompi/mca/btl/tcp/help-mpi-btl-tcp.txt
Jeff Squyres c8dc1905f0 Fixes trac:3494: If we get 0 bytes back for the ACK, it doesn't
necessarily mean an error -- it could (and usually does) mean that the
peer realized that we both initiated a connect at the same time, and
therefore it decided to hang up.

I also added a friendly show_help error message for other cases where
recv_blocking() fails (i.e., "Something went wrong. Kaboom! Your job
will abort...").

This commit was SVN r28023.

The following Trac tickets were found above:
  Ticket 3494 --> https://svn.open-mpi.org/trac/ompi/ticket/3494
2013-02-02 01:19:03 +00:00

39 строки
850 B
Plaintext

# -*- text -*-
#
# Copyright (c) 2009-2013 Cisco Systems, Inc. All rights reserved.
# $COPYRIGHT$
#
# Additional copyrights may follow
#
# $HEADER$
#
# This is the US/English help file for Open MPI's TCP support
# (the openib BTL).
#
[invalid if_inexclude]
WARNING: An invalid value was given for btl_tcp_if_%s. This
value will be ignored.
Local host: %s
Value: %s
Message: %s
#
[invalid minimum port]
WARNING: An invalid value was given for the btl_tcp_port_min_%s. Legal
values are in the range [1 .. 2^16-1]. This value will be ignored
(reset to the default value of 1024).
Local host: %s
Value: %d
[client connect fail]
WARNING: Open MPI failed to TCP connect to a peer MPI process. This
should not happen.
Your Open MPI job may now fail.
Local host: %s
PID: %d
Message: %s
Error: %s (%d)
#