1
1
openmpi/orte/mca/rmgr
Ralph Castain ca5b4358fa Need to revise the display-map-at-launch option so it is active not only for the initial launch, but applies to any subsequent comm_spawn events too.
Add placeholders for the new orte tools. These don't actually do anything yet - in fact, I have set the .ompi_ignore so that you won't compile them (I have set a .ompi_unignore for me). Please let me know if you encounter any trouble with this - the ompi_ignore's should protect everyone.

This commit was SVN r12616.
2006-11-17 02:58:46 +00:00
..
base Sign of old age.....fix some compiler complaints 2006-11-15 22:28:14 +00:00
cnos Modify the RMGR components to allow job setup with a given jobid, and add another attribute so that we can setup triggers without launching. 2006-11-13 18:51:18 +00:00
proxy Need to revise the display-map-at-launch option so it is active not only for the initial launch, but applies to any subsequent comm_spawn events too. 2006-11-17 02:58:46 +00:00
urm Need to revise the display-map-at-launch option so it is active not only for the initial launch, but applies to any subsequent comm_spawn events too. 2006-11-17 02:58:46 +00:00
Makefile.am Fix the bug that caused mpirun to hang when a remote executable wasn't found using the rsh launcher. Will now test on a remote node 2006-10-11 18:43:13 +00:00
rmgr_types.h Modify the RMGR components to allow job setup with a given jobid, and add another attribute so that we can setup triggers without launching. 2006-11-13 18:51:18 +00:00
rmgr.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). 2006-11-14 19:34:59 +00:00