Gilles Gouaillardet 27b4727fcf orte/orted: fix misc memory leak ... as reported by Coverity with CID 743448		2015-06-17 11:17:55 +09:00
..
pmix	Fat SMPs (i.e., systems with nodes containing large numbers of cpus) were failing to start due to connection failures of the opal/pmix support. Root cause was that (a) we were setting the client socket to non-blocking before calling connect, and (b) the server was using the event library to harvest the accepts, and also did the handshake while in that event. So the server would backup beyond the connection backlog limit, and we would fail.	2015-05-29 14:37:14 -07:00
help-orted.txt	Okay, since a certain other RM out there made a fuss about being able to lock their daemons to specified cores, offer the same option here. The MCA param orte_daemon_cores can be used to specify which core(s) you want the orte daemons to use. This will have no bearing on the application procs - unbound will remain unbound, and binding directives will be applied to the apps.	2014-01-30 23:50:14 +00:00
Makefile.am	configury: new OPAL_SET_LIB_PREFIX/ORTE_SET_LIB_PREFIX macros	2014-10-22 10:32:19 -07:00
orted_comm.c	Cleanup the pretty-print of odls cmds as some were missing. Add a new cmd to terminate the DVM, which the HNP will use to trun around and issue an xcast to the DVM.	2015-02-10 08:27:13 -08:00
orted_main.c	orte/orted: fix misc memory leak	2015-06-17 11:17:55 +09:00
orted.h	Remove stale code - message arrival time doesn't really mean much anymore.	2013-01-24 23:02:02 +00:00