Ralph Castain 9f3dcd147a Round and round the mulberry bush we go... ... Fix comm_spawn by singletons. orte_init does some voodoo to let the system know about localhost when we are a singleton. This includes allocating it so that any comm_spawn'd children can use their parent "allocation". Unfortunately, the fix that bproc needs (due to that smr filling up the node segment!) causes the singleton startup to fail. The fix is to just have the singleton startup force an allocation of its localhost. Only issue here is: what happens if we are in a persistent universe? The singleton will now overwrite any prior info on slots used on localhost by other jobs (won't affect anything else). The answer, of course, is to do something more intelligent - lookup localhost on the registry and just update its info instead of overwriting it. Something for another day (or month....or year) This commit was SVN r12644.		2006-11-21 21:51:58 +00:00
..
class	And ORTE is ready for prime-time. All Windows tricks are in:	2006-08-23 03:32:36 +00:00
dss	Remove svn:executable from a bunch of files.	2006-11-17 11:01:39 +00:00
etc	Next step in the project split, mainly source code re-arranging	2006-02-12 01:33:29 +00:00
include	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
mca	cleanup unused variables	2006-11-21 20:51:39 +00:00
runtime	Round and round the mulberry bush we go...	2006-11-21 21:51:58 +00:00
test	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
tools	Bring ortehalt to a preliminary capability. It will corectly order a persistent daemon to exit cleanly. Need to now interface it to orterun, clean up a few things here and there	2006-11-18 04:47:51 +00:00
util	Cleanup the problem of connecting to default universes.	2006-11-06 15:28:38 +00:00
Doxyfile	Fix the broken Doxyfile so people can generate what little code base documentation we have :-)	2006-04-13 12:52:17 +00:00
Makefile.am	* Fix a small bug George noticed - if you change the prefix (or any of the	2006-03-12 04:35:01 +00:00