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

53 строки
1.5 KiB
Plaintext
Исходник Обычный вид История

- Add an opal_show_help() to the pls fork module to explain what went wrong when the execv to start the application fails. - Add a couple opal_show_help()'s to indicate when not enough slots/nodes are available to satisfy a request. This commit was SVN r7555.
2005-09-30 18:30:21 +04:00
# -*- text -*-
#
Change the behavior of orterun (mpirun, mpirexec) to search for argv[0] and the cwd on the target node (i.e., the node where the executable will be running in all systems except BProc, where the searches are run on the node where orterun is invoked). - fork pls now does cwd and argv[0] search in orted - bproc pls does cwd and argv[0] search in orterun - cwd behavior slightly different: - if user specifies a -wdir to orterun, we chdir() to there; if we can't for some reason, abort - if user does not specify a -wdir, try to chdir() to the dir where orterun was invoked. If we can't for some reason (e.g., it doesn't exist on the target node), then try to chdir($HOME). If we can't do that, then just live with whatever default directory we were put in. This commit was SVN r9068.
2006-02-16 23:40:23 +03:00
# Copyright (c) 2004-2006 The Trustees of Indiana University and Indiana
Update the copyright notices for IU and UTK. This commit was SVN r7999.
2005-11-05 22:57:48 +03:00
# 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.
- Add an opal_show_help() to the pls fork module to explain what went wrong when the execv to start the application fails. - Add a couple opal_show_help()'s to indicate when not enough slots/nodes are available to satisfy a request. This commit was SVN r7555.
2005-09-30 18:30:21 +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$
#
Here is the major MAD-cure commit. I have written plenty about it, so I refer you here to those messages for a description of everything that was done. This commit was SVN r11661.
2006-09-15 01:29:51 +04:00
# This is the US/English general help file for Open RTE's orted launcher.
- Add an opal_show_help() to the pls fork module to explain what went wrong when the execv to start the application fails. - Add a couple opal_show_help()'s to indicate when not enough slots/nodes are available to satisfy a request. This commit was SVN r7555.
2005-09-30 18:30:21 +04:00
#
Here is the major MAD-cure commit. I have written plenty about it, so I refer you here to those messages for a description of everything that was done. This commit was SVN r11661.
2006-09-15 01:29:51 +04:00
[odls-default:chdir-error]
Change the behavior of orterun (mpirun, mpirexec) to search for argv[0] and the cwd on the target node (i.e., the node where the executable will be running in all systems except BProc, where the searches are run on the node where orterun is invoked). - fork pls now does cwd and argv[0] search in orted - bproc pls does cwd and argv[0] search in orterun - cwd behavior slightly different: - if user specifies a -wdir to orterun, we chdir() to there; if we can't for some reason, abort - if user does not specify a -wdir, try to chdir() to the dir where orterun was invoked. If we can't for some reason (e.g., it doesn't exist on the target node), then try to chdir($HOME). If we can't do that, then just live with whatever default directory we were put in. This commit was SVN r9068.
2006-02-16 23:40:23 +03:00
Failed to change to the working directory:
- Add an opal_show_help() to the pls fork module to explain what went wrong when the execv to start the application fails. - Add a couple opal_show_help()'s to indicate when not enough slots/nodes are available to satisfy a request. This commit was SVN r7555.
2005-09-30 18:30:21 +04:00
Change the behavior of orterun (mpirun, mpirexec) to search for argv[0] and the cwd on the target node (i.e., the node where the executable will be running in all systems except BProc, where the searches are run on the node where orterun is invoked). - fork pls now does cwd and argv[0] search in orted - bproc pls does cwd and argv[0] search in orterun - cwd behavior slightly different: - if user specifies a -wdir to orterun, we chdir() to there; if we can't for some reason, abort - if user does not specify a -wdir, try to chdir() to the dir where orterun was invoked. If we can't for some reason (e.g., it doesn't exist on the target node), then try to chdir($HOME). If we can't do that, then just live with whatever default directory we were put in. This commit was SVN r9068.
2006-02-16 23:40:23 +03:00
Host: %s
Directory: %s
- Add an opal_show_help() to the pls fork module to explain what went wrong when the execv to start the application fails. - Add a couple opal_show_help()'s to indicate when not enough slots/nodes are available to satisfy a request. This commit was SVN r7555.
2005-09-30 18:30:21 +04:00
Change the behavior of orterun (mpirun, mpirexec) to search for argv[0] and the cwd on the target node (i.e., the node where the executable will be running in all systems except BProc, where the searches are run on the node where orterun is invoked). - fork pls now does cwd and argv[0] search in orted - bproc pls does cwd and argv[0] search in orterun - cwd behavior slightly different: - if user specifies a -wdir to orterun, we chdir() to there; if we can't for some reason, abort - if user does not specify a -wdir, try to chdir() to the dir where orterun was invoked. If we can't for some reason (e.g., it doesn't exist on the target node), then try to chdir($HOME). If we can't do that, then just live with whatever default directory we were put in. This commit was SVN r9068.
2006-02-16 23:40:23 +03:00
The error returned was "%s". Execution will now abort.
Here is the major MAD-cure commit. I have written plenty about it, so I refer you here to those messages for a description of everything that was done. This commit was SVN r11661.
2006-09-15 01:29:51 +04:00
[odls-default:argv0-not-accessible]
Change the behavior of orterun (mpirun, mpirexec) to search for argv[0] and the cwd on the target node (i.e., the node where the executable will be running in all systems except BProc, where the searches are run on the node where orterun is invoked). - fork pls now does cwd and argv[0] search in orted - bproc pls does cwd and argv[0] search in orterun - cwd behavior slightly different: - if user specifies a -wdir to orterun, we chdir() to there; if we can't for some reason, abort - if user does not specify a -wdir, try to chdir() to the dir where orterun was invoked. If we can't for some reason (e.g., it doesn't exist on the target node), then try to chdir($HOME). If we can't do that, then just live with whatever default directory we were put in. This commit was SVN r9068.
2006-02-16 23:40:23 +03:00
Failed to find or execute the following executable:
Host: %s
Executable: %s
Cannot continue.
Here is the major MAD-cure commit. I have written plenty about it, so I refer you here to those messages for a description of everything that was done. This commit was SVN r11661.
2006-09-15 01:29:51 +04:00
[odls-default:could-not-kill]
Change the behavior of orterun (mpirun, mpirexec) to search for argv[0] and the cwd on the target node (i.e., the node where the executable will be running in all systems except BProc, where the searches are run on the node where orterun is invoked). - fork pls now does cwd and argv[0] search in orted - bproc pls does cwd and argv[0] search in orterun - cwd behavior slightly different: - if user specifies a -wdir to orterun, we chdir() to there; if we can't for some reason, abort - if user does not specify a -wdir, try to chdir() to the dir where orterun was invoked. If we can't for some reason (e.g., it doesn't exist on the target node), then try to chdir($HOME). If we can't do that, then just live with whatever default directory we were put in. This commit was SVN r9068.
2006-02-16 23:40:23 +03:00
WARNING: A process refused to die!
Host: %s
PID: %d
- Add an opal_show_help() to the pls fork module to explain what went wrong when the execv to start the application fails. - Add a couple opal_show_help()'s to indicate when not enough slots/nodes are available to satisfy a request. This commit was SVN r7555.
2005-09-30 18:30:21 +04:00
Change the behavior of orterun (mpirun, mpirexec) to search for argv[0] and the cwd on the target node (i.e., the node where the executable will be running in all systems except BProc, where the searches are run on the node where orterun is invoked). - fork pls now does cwd and argv[0] search in orted - bproc pls does cwd and argv[0] search in orterun - cwd behavior slightly different: - if user specifies a -wdir to orterun, we chdir() to there; if we can't for some reason, abort - if user does not specify a -wdir, try to chdir() to the dir where orterun was invoked. If we can't for some reason (e.g., it doesn't exist on the target node), then try to chdir($HOME). If we can't do that, then just live with whatever default directory we were put in. This commit was SVN r9068.
2006-02-16 23:40:23 +03:00
This process may still be running and/or consuming resources.
A bit more cleanup for that last patch. * num_children should really be an int instead of size_t since 'size_t' is not signed and num_children can (in rare cases) drop below 0, and don't want it to roll around to MAX_INT or some such. * I figured out that this problem only happened to me because I use the pls_fork_reap_timeout MCA parameter and thus the only time that the code in pls_fork_module.c to waitpid is executed is if this is not set to 0 (I had it set to 1 to give my procs time to exit). I adjusted the loop from while{...} to do{...}while; so that it is executed at least once for consistency. * de-register the SIGCHILD callback for the pid before we attempt to kill it, so that we don't leave the door open for both the waitpids (the one in the callback, and the one in this function) to race to see who can wait on the child. * Move the 'thread release' to outside the for loop for a bit of an optimization, and always set the value to 0 since we want to finish after this function. * Added a help message for the case when we can't send a kill() signal to the process. Should never happen, but all is possible in the wild wild west of HPC. This commit was SVN r10666.
2006-07-06 01:38:23 +04:00
Here is the major MAD-cure commit. I have written plenty about it, so I refer you here to those messages for a description of everything that was done. This commit was SVN r11661.
2006-09-15 01:29:51 +04:00
[odls-default:could-not-send-kill]
A bit more cleanup for that last patch. * num_children should really be an int instead of size_t since 'size_t' is not signed and num_children can (in rare cases) drop below 0, and don't want it to roll around to MAX_INT or some such. * I figured out that this problem only happened to me because I use the pls_fork_reap_timeout MCA parameter and thus the only time that the code in pls_fork_module.c to waitpid is executed is if this is not set to 0 (I had it set to 1 to give my procs time to exit). I adjusted the loop from while{...} to do{...}while; so that it is executed at least once for consistency. * de-register the SIGCHILD callback for the pid before we attempt to kill it, so that we don't leave the door open for both the waitpids (the one in the callback, and the one in this function) to race to see who can wait on the child. * Move the 'thread release' to outside the for loop for a bit of an optimization, and always set the value to 0 since we want to finish after this function. * Added a help message for the case when we can't send a kill() signal to the process. Should never happen, but all is possible in the wild wild west of HPC. This commit was SVN r10666.
2006-07-06 01:38:23 +04:00
WARNING: A process refused the kill SIGTERM signal!
This should never happen unless the application is changing the
parent/child relationship permissions.
Host: %s
PID: %d
Errno: %d
This process may still be running and/or consuming resources.
Копировать постоянную ссылку