ports/openmpi
ports/openmpi
1
1
Форкнуть 0
Код Релизы Активность
7818779760
openmpi/orte/runtime/help-orte-runtime.txt

61 строка
2.1 KiB
Plaintext
Исходник Обычный вид История

Implement an opal_show_help() (like is done in ompi_mpi_init) for error handling in opal_init and both stages of orte_init. Some of the functions in opal_init are void or return a bool (opal_output_init, but always returns true.. eh?), so I don't check them. This commit was SVN r7638.
2005-10-05 17:56:35 +04:00
# -*- text -*-
#
Update the copyright notices for IU and UTK. This commit was SVN r7999.
2005-11-05 22:57:48 +03:00
# Copyright (c) 2004-2005 The Trustees of Indiana University and Indiana
# University Research and Technology
# Corporation. All rights reserved.
# Copyright (c) 2004-2005 The University of Tennessee and The University
# of Tennessee Research Foundation. All rights
# reserved.
Implement an opal_show_help() (like is done in ompi_mpi_init) for error handling in opal_init and both stages of orte_init. Some of the functions in opal_init are void or return a bool (opal_output_init, but always returns true.. eh?), so I don't check them. This commit was SVN r7638.
2005-10-05 17:56:35 +04:00
# 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$
#
# This is the US/English general help file for Open MPI.
#
[orte_init:startup:internal-failure]
It looks like orte_init failed for some reason; your parallel process is
likely to abort. There are many reasons that a parallel process can
fail during orte_init; some of which are due to configuration or
environment problems. This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
Open MPI developer):
%s failed
Complete modifications for failed-to-start of applications. Modifications for failed-to-start of orteds coming next. This completes the minor changes required to the PLS components. Basically, there is a small change required to the parameter list of the orted cmd functions. I caught and did it for xcpu and poe, in addition to the components listed in my email - so I think that only leaves xgrid unconverted. The orted fail-to-start mods will also make changes in the PLS components, but those can be localized so they come in one at a time. This commit was SVN r14499.
2007-04-25 00:53:54 +04:00
--> Returned value %s (%d) instead of ORTE_SUCCESS
It is okay for us to init the ORTE mca params multiple times. Indeed, it is absolutely required by orterun as the first time has to be done prior to parsing the command line, which means that the mca values haven't been parsed yet! Add ability for sys admins to prohibit putting session directories under specified locations. Thus, they can now protect parallel file systems from foolish user mistakes. This commit was SVN r18721.
2008-06-24 21:50:56 +04:00
#
#
[orte:session:dir:prohibited]
The specified location for the temporary directories required by Open MPI
is on the list of prohibited locations:
Location given: %s
Prohibited locations: %s
Implement an opal_show_help() (like is done in ompi_mpi_init) for error handling in opal_init and both stages of orte_init. Some of the functions in opal_init are void or return a bool (opal_output_init, but always returns true.. eh?), so I don't check them. This commit was SVN r7638.
2005-10-05 17:56:35 +04:00
It is okay for us to init the ORTE mca params multiple times. Indeed, it is absolutely required by orterun as the first time has to be done prior to parsing the command line, which means that the mca values haven't been parsed yet! Add ability for sys admins to prohibit putting session directories under specified locations. Thus, they can now protect parallel file systems from foolish user mistakes. This commit was SVN r18721.
2008-06-24 21:50:56 +04:00
If you believe this is in error, please contact your system administrator
to have the list of prohibited locations changed. Otherwise, please identify
a different location to be used (use -h to see the cmd line option), or
simply let the system pick a default location.
Expose the nidmap and pidmap as orte globals so that components in other frameworks can access and/or manipulate them without forcing API modifications - modify the individual ess components that were affected so they use the global variables. Add a list of attributes to the nids for storing node-related data (e.g., modex attrs), and define a new object for that purpose. Consolidate the nid/pid lookup code with the rest of the nid/pid code so that changes are easier to track. Add the ability to send cluster profile info as part of the nidmap. Cleanup the setup and teardown of the new global nidmap and pidmap objects. This commit was SVN r20219.
2009-01-07 17:58:38 +03:00
#
#
[orte_nidmap:file-cant-open]
Unable to open the file that was to contain the cluster's profile. The file
name we were given was:
FILE: %s
Please check to ensure this file exists and has appropriate read permissions.
#
[orte_nidmap:unable-read-file]
An error occurred while trying to read the file containing the cluster's profile.
The file we were reading was:
FILE: %s
Please check that this file was correctly generated.
Копировать постоянную ссылку