Brian Barrett f6a5d58885 Rather than set the connect event timeout number to something big and hoping ... its bigger than the timeout for the connect() call, just don't register the handler by default and fall back to connect() timing out. Should give much happier performance on big clusters. This commit was SVN r13639.		2007-02-13 18:36:50 +00:00
..
configure.m4	Update the copyright notices for IU and UTK.	2005-11-05 19:57:48 +00:00
configure.params	Remove unneeded PARAM_INIT_FILE variable in configure.params files used by	2007-01-08 03:44:22 +00:00
Makefile.am	Rename liborte to libopen-rte and libopal to libopen-pal per telecon today	2006-12-05 18:27:24 +00:00
oob_tcp_addr.c	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
oob_tcp_addr.h	Hand-pack the connection information for each peer rather than just	2006-10-25 15:09:30 +00:00
oob_tcp_hdr.h	Rename OMPI_PROCESS_NAME_{HTON, NTOH} macros to ORTE_PROCESS_NAME_{HTON, NTOH}	2006-11-22 03:03:21 +00:00
oob_tcp_msg.c	Print out error string rather than errno for TCP-related errors, making it easier for both the user and us to debug issues with BTL and OOB issues...	2006-12-14 18:20:43 +00:00
oob_tcp_msg.h	* use opal_free_list_item_t as the type of items stored in an opal_free_list_t,	2006-07-17 21:51:50 +00:00
oob_tcp_peer.c	Rather than set the connect event timeout number to something big and hoping	2007-02-13 18:36:50 +00:00
oob_tcp_peer.h	And ORTE is ready for prime-time. All Windows tricks are in:	2006-08-23 03:32:36 +00:00
oob_tcp_ping.c	Print out error string rather than errno for TCP-related errors, making it easier for both the user and us to debug issues with BTL and OOB issues...	2006-12-14 18:20:43 +00:00
oob_tcp_recv.c	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
oob_tcp_send.c	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
oob_tcp.c	Rather than set the connect event timeout number to something big and hoping	2007-02-13 18:36:50 +00:00
oob_tcp.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