5e6928d710
Basically, the method employed here is to have a recv create a zero-time timer event that causes the event library to execute a function that processes the message once the recv returns. Thus, any action taken as a result of processing the message occur outside of a recv. Created two new macros to assist: ORTE_MESSAGE_EVENT: creates the zero-time event, passing info in a new orte_message_event_t object ORTE_PROGRESSED_WAIT: while waiting for specified conditions, just calls progress so messages can be recv'd. Also fixed the failed_launch function as we no longer block in the orted callback function. Updated the error messages to reflect revision. No change in API to this function, but PLM "owners" may want to check their internal error messages to avoid duplication and excessive output. This has been tested on Mac, TM, and SLURM. This commit was SVN r17647.
76 строки
3.1 KiB
Plaintext
76 строки
3.1 KiB
Plaintext
# -*- 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$
|
|
#
|
|
# Additional copyrights may follow
|
|
#
|
|
# $HEADER$
|
|
#
|
|
[no-available-pls]
|
|
No available launching agents were found.
|
|
|
|
This is an unusual error; it means that Open RTE was unable to find
|
|
any mechanism to launch proceses, and therefore is unable to start the
|
|
process(es) required by your application.
|
|
#
|
|
[daemon-died-no-signal]
|
|
A daemon (pid %d) died unexpectedly with status %d while attempting
|
|
to launch so we are aborting.
|
|
|
|
There may be more information reported by the environment (see above).
|
|
|
|
This may be because the daemon was unable to find all the needed shared
|
|
libraries on the remote node. You may set your LD_LIBRARY_PATH to have the
|
|
location of the shared libraries on the remote nodes and this will
|
|
automatically be forwarded to the remote nodes.
|
|
#
|
|
[daemon-died-signal-core]
|
|
A daemon (pid %d) died unexpectedly on signal %d (with core) while
|
|
attempting to launch so we are aborting.
|
|
|
|
There may be more information reported by the environment (see above).
|
|
|
|
This may be because the daemon was unable to find all the needed shared
|
|
libraries on the remote node. You may set your LD_LIBRARY_PATH to have the
|
|
location of the shared libraries on the remote nodes and this will
|
|
automatically be forwarded to the remote nodes.
|
|
#
|
|
[daemon-died-signal]
|
|
A daemon (pid %d) died unexpectedly on signal %d while attempting to
|
|
launch so we are aborting.
|
|
|
|
There may be more information reported by the environment (see above).
|
|
|
|
This may be because the daemon was unable to find all the needed shared
|
|
libraries on the remote node. You may set your LD_LIBRARY_PATH to have the
|
|
location of the shared libraries on the remote nodes and this will
|
|
automatically be forwarded to the remote nodes.
|
|
#
|
|
[incomplete-exit-cmd]
|
|
One or more daemons could not be ordered to exit. This can be caused by a
|
|
number of rather rare problems, but typically is caused by a daemon having
|
|
died due to the failure of a node or its communications. This could result
|
|
in an incomplete cleanup on the affected nodes. Please see below for a list
|
|
of nodes which may require additional cleanup.
|
|
|
|
We are truly sorry for the inconvenience.
|
|
#
|
|
[incomplete-kill-procs-cmd]
|
|
One or more daemons could not be ordered to kill their local processes.
|
|
This can be caused by a number of rather rare problems, but typically
|
|
is caused by a daemon having died due to the failure of a node or its
|
|
communications. This could result in an incomplete cleanup on the affected
|
|
nodes. Additional information may be available below.
|
|
|
|
We are truly sorry for the inconvenience.
|