Li-Ta Lo 6df4e80727 new XCPU PLS and SDS to work with libxcpu ...

This commit was SVN r12905.

2006-12-21 00:05:36 +00:00

..

base

Repair support for Bproc 4 on 64-bit systems. Update the SMR framework to actually support the begin_monitoring API. Implement the get/set_node_state APIs.

2006-12-15 02:34:14 +00:00

bproc

Fix some errors in the bproc components that prevented compiling. Thought I had already done this, but either those changes were lost when I did the merge, or my old man's memory is fading....

2006-12-15 19:40:04 +00:00

cnos

Rename liborte to libopen-rte and libopal to libopen-pal per telecon today

2006-12-05 18:27:24 +00:00

gridengine

Rename liborte to libopen-rte and libopal to libopen-pal per telecon today

2006-12-05 18:27:24 +00:00

poe

Rename liborte to libopen-rte and libopal to libopen-pal per telecon today

2006-12-05 18:27:24 +00:00

proxy

Rename liborte to libopen-rte and libopal to libopen-pal per telecon today

2006-12-05 18:27:24 +00:00

rsh

Fix the fix to remove compiler warning - an incorrect "\" was placed in the command string.

2006-12-08 04:17:38 +00:00

slurm

Rename liborte to libopen-rte and libopal to libopen-pal per telecon today

2006-12-05 18:27:24 +00:00

tm

Rename liborte to libopen-rte and libopal to libopen-pal per telecon today

2006-12-05 18:27:24 +00:00

xcpu

new XCPU PLS and SDS to work with libxcpu

2006-12-21 00:05:36 +00:00

xgrid

Rename liborte to libopen-rte and libopal to libopen-pal per telecon today

2006-12-05 18:27:24 +00:00

Makefile.am

Here is the major MAD-cure commit. I have written plenty about it, so I refer you here to those messages for a description of everything that was done.

2006-09-14 21:29:51 +00:00

pls_types.h

Here is the major MAD-cure commit. I have written plenty about it, so I refer you here to those messages for a description of everything that was done.

2006-09-14 21:29:51 +00:00

pls.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