2005-01-13 15:30:49 +00:00
|
|
|
/*
|
2005-11-05 19:57:48 +00:00
|
|
|
* Copyright (c) 2004-2005 The Trustees of Indiana University and Indiana
|
|
|
|
* University Research and Technology
|
|
|
|
* Corporation. All rights reserved.
|
2006-08-24 16:38:08 +00:00
|
|
|
* Copyright (c) 2004-2006 The University of Tennessee and The University
|
2005-11-05 19:57:48 +00:00
|
|
|
* of Tennessee Research Foundation. All rights
|
|
|
|
* reserved.
|
2005-01-13 15:30:49 +00:00
|
|
|
* Copyright (c) 2004-2005 High Performance Computing Center Stuttgart,
|
|
|
|
* University of Stuttgart. All rights reserved.
|
2005-03-24 12:43:37 +00:00
|
|
|
* Copyright (c) 2004-2005 The Regents of the University of California.
|
|
|
|
* All rights reserved.
|
2005-01-13 15:30:49 +00:00
|
|
|
* $COPYRIGHT$
|
|
|
|
*
|
|
|
|
* Additional copyrights may follow
|
|
|
|
*
|
|
|
|
* $HEADER$
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include "ompi_config.h"
|
Bring over the update to terminate orteds that are generated by a dynamic spawn such as comm_spawn. This introduces the concept of a job "family" - i.e., jobs that have a parent/child relationship. Comm_spawn'ed jobs have a parent (the one that spawned them). We track that relationship throughout the lineage - i.e., if a comm_spawned job in turn calls comm_spawn, then it has a parent (the one that spawned it) and a "root" job (the original job that started things).
Accordingly, there are new APIs to the name service to support the ability to get a job's parent, root, immediate children, and all its descendants. In addition, the terminate_job, terminate_orted, and signal_job APIs for the PLS have been modified to accept attributes that define the extent of their actions. For example, doing a "terminate_job" with an attribute of ORTE_NS_INCLUDE_DESCENDANTS will terminate the given jobid AND all jobs that descended from it.
I have tested this capability on a MacBook under rsh, Odin under SLURM, and LANL's Flash (bproc). It worked successfully on non-MPI jobs (both simple and including a spawn), and MPI jobs (again, both simple and with a spawn).
This commit was SVN r12597.
2006-11-14 19:34:59 +00:00
|
|
|
#include "orte/mca/ns/ns_types.h"
|
2006-02-12 01:33:29 +00:00
|
|
|
#include "orte/mca/iof/iof.h"
|
2006-08-24 16:38:08 +00:00
|
|
|
#include "ompi/constants.h"
|
2005-01-13 15:30:49 +00:00
|
|
|
|
2006-08-24 16:38:08 +00:00
|
|
|
#if defined(__WINDOWS__)
|
|
|
|
#include <io.h>
|
|
|
|
#endif /* defined(__WINDOWS__) */
|
2005-01-13 15:30:49 +00:00
|
|
|
|
|
|
|
int ompi_mpi_init_io(void)
|
|
|
|
{
|
|
|
|
int fds[2];
|
|
|
|
int rc;
|
|
|
|
|
2005-01-25 20:01:06 +00:00
|
|
|
/* We need to add a NULL component for iof. Until then, this will have to do */
|
2005-01-13 15:30:49 +00:00
|
|
|
/* setup stdin */
|
|
|
|
rc = pipe(fds);
|
|
|
|
if(rc < 0) {
|
|
|
|
return OMPI_ERR_OUT_OF_RESOURCE;
|
|
|
|
}
|
|
|
|
dup2(fds[0], 0);
|
|
|
|
close(fds[0]);
|
|
|
|
|
|
|
|
rc = mca_iof.iof_publish(
|
Bring over the update to terminate orteds that are generated by a dynamic spawn such as comm_spawn. This introduces the concept of a job "family" - i.e., jobs that have a parent/child relationship. Comm_spawn'ed jobs have a parent (the one that spawned them). We track that relationship throughout the lineage - i.e., if a comm_spawned job in turn calls comm_spawn, then it has a parent (the one that spawned it) and a "root" job (the original job that started things).
Accordingly, there are new APIs to the name service to support the ability to get a job's parent, root, immediate children, and all its descendants. In addition, the terminate_job, terminate_orted, and signal_job APIs for the PLS have been modified to accept attributes that define the extent of their actions. For example, doing a "terminate_job" with an attribute of ORTE_NS_INCLUDE_DESCENDANTS will terminate the given jobid AND all jobs that descended from it.
I have tested this capability on a MacBook under rsh, Odin under SLURM, and LANL's Flash (bproc). It worked successfully on non-MPI jobs (both simple and including a spawn), and MPI jobs (again, both simple and with a spawn).
This commit was SVN r12597.
2006-11-14 19:34:59 +00:00
|
|
|
OMPI_PROC_MY_NAME,
|
2005-01-13 15:30:49 +00:00
|
|
|
MCA_IOF_SINK,
|
|
|
|
MCA_IOF_STDIN,
|
|
|
|
fds[1]);
|
|
|
|
if(rc != OMPI_SUCCESS)
|
|
|
|
return rc;
|
|
|
|
|
|
|
|
/* setup stdout */
|
|
|
|
rc = pipe(fds);
|
|
|
|
if(rc < 0) {
|
|
|
|
return OMPI_ERR_OUT_OF_RESOURCE;
|
|
|
|
}
|
|
|
|
dup2(fds[1], 1);
|
|
|
|
close(fds[1]);
|
|
|
|
|
|
|
|
rc = mca_iof.iof_publish(
|
Bring over the update to terminate orteds that are generated by a dynamic spawn such as comm_spawn. This introduces the concept of a job "family" - i.e., jobs that have a parent/child relationship. Comm_spawn'ed jobs have a parent (the one that spawned them). We track that relationship throughout the lineage - i.e., if a comm_spawned job in turn calls comm_spawn, then it has a parent (the one that spawned it) and a "root" job (the original job that started things).
Accordingly, there are new APIs to the name service to support the ability to get a job's parent, root, immediate children, and all its descendants. In addition, the terminate_job, terminate_orted, and signal_job APIs for the PLS have been modified to accept attributes that define the extent of their actions. For example, doing a "terminate_job" with an attribute of ORTE_NS_INCLUDE_DESCENDANTS will terminate the given jobid AND all jobs that descended from it.
I have tested this capability on a MacBook under rsh, Odin under SLURM, and LANL's Flash (bproc). It worked successfully on non-MPI jobs (both simple and including a spawn), and MPI jobs (again, both simple and with a spawn).
This commit was SVN r12597.
2006-11-14 19:34:59 +00:00
|
|
|
OMPI_PROC_MY_NAME,
|
2005-01-13 15:30:49 +00:00
|
|
|
MCA_IOF_SOURCE,
|
|
|
|
MCA_IOF_STDOUT,
|
|
|
|
fds[0]);
|
|
|
|
if(rc != OMPI_SUCCESS)
|
|
|
|
return rc;
|
|
|
|
|
|
|
|
/* setup stderr */
|
|
|
|
rc = pipe(fds);
|
|
|
|
if(rc < 0) {
|
|
|
|
return OMPI_ERR_OUT_OF_RESOURCE;
|
|
|
|
}
|
|
|
|
dup2(fds[1], 2);
|
|
|
|
close(fds[1]);
|
|
|
|
|
|
|
|
rc = mca_iof.iof_publish(
|
Bring over the update to terminate orteds that are generated by a dynamic spawn such as comm_spawn. This introduces the concept of a job "family" - i.e., jobs that have a parent/child relationship. Comm_spawn'ed jobs have a parent (the one that spawned them). We track that relationship throughout the lineage - i.e., if a comm_spawned job in turn calls comm_spawn, then it has a parent (the one that spawned it) and a "root" job (the original job that started things).
Accordingly, there are new APIs to the name service to support the ability to get a job's parent, root, immediate children, and all its descendants. In addition, the terminate_job, terminate_orted, and signal_job APIs for the PLS have been modified to accept attributes that define the extent of their actions. For example, doing a "terminate_job" with an attribute of ORTE_NS_INCLUDE_DESCENDANTS will terminate the given jobid AND all jobs that descended from it.
I have tested this capability on a MacBook under rsh, Odin under SLURM, and LANL's Flash (bproc). It worked successfully on non-MPI jobs (both simple and including a spawn), and MPI jobs (again, both simple and with a spawn).
This commit was SVN r12597.
2006-11-14 19:34:59 +00:00
|
|
|
OMPI_PROC_MY_NAME,
|
2005-01-13 15:30:49 +00:00
|
|
|
MCA_IOF_SOURCE,
|
|
|
|
MCA_IOF_STDERR,
|
|
|
|
fds[0]);
|
|
|
|
if(rc != OMPI_SUCCESS)
|
|
|
|
return rc;
|
2006-08-24 16:38:08 +00:00
|
|
|
|
2005-01-13 15:30:49 +00:00
|
|
|
return OMPI_SUCCESS;
|
|
|
|
}
|
|
|
|
|
|
|
|
|