openmpi

Brian Barrett 566a050c23 Next step in the project split, mainly source code re-arranging

- move files out of toplevel include/ and etc/, moving it into the
    sub-projects
  - rather than including config headers with <project>/include, 
    have them as <project>
  - require all headers to be included with a project prefix, with
    the exception of the config headers ({opal,orte,ompi}_config.h
    mpi.h, and mpif.h)

This commit was SVN r8985.

2006-02-12 01:33:29 +00:00

Makefile.am

Merge in the new data support subsystem for ORTE. MPI folks should not notice a difference. Longer explanation will be sent to developers mailing list.

2006-02-07 03:32:36 +00:00

opal_init_finalize.c

Update the copyright notices for IU and UTK.

2005-11-05 19:57:48 +00:00

orte_init_finalize.c

Merge in the new data support subsystem for ORTE. MPI folks should not notice a difference. Longer explanation will be sent to developers mailing list.

2006-02-07 03:32:36 +00:00

README

Merge in the new data support subsystem for ORTE. MPI folks should not notice a difference. Longer explanation will be sent to developers mailing list.

2006-02-07 03:32:36 +00:00

sigchld.c

Next step in the project split, mainly source code re-arranging

2006-02-12 01:33:29 +00:00

start_shut.c

Update the copyright notices for IU and UTK.

2005-11-05 19:57:48 +00:00

README

The functions in this directory are all intended to test registry operations against a persistent seed. Thus, they perform a system init/finalize. The functions in the directory above this one should be used to test basic registry operations within the replica - they will isolate the replica so as to avoid the communications issues and the init/finalize problems in other subsystems that may cause problems here.

To run these tests, you need to first start a persistent daemon. This can be done using the command:

orted --seed --scope public --persistent

The daemon will "daemonize" itself and establish the registry (as well as other central services) replica, and then return a system prompt. You can then run any of these functions. If desired, you can utilize gdb and/or debug options on the persistent orted to watch/debug replica operations as well.