Gotcha; thanks for the explanation.
The capabilities you added sounds good for the moment; I'm sure we'll
think of more over time...
On Jan 22, 2008, at 10:19 AM, Ralph H Castain wrote:
On 1/19/08 6:31 AM, "Jeff Squyres" wrote:
Ralph --
I'm a little confused as to what you're provid
On 1/19/08 6:31 AM, "Jeff Squyres" wrote:
> Ralph --
>
> I'm a little confused as to what you're providing. In all 3 of the
> scenarios you describe, you're saying that the external tool can
> connect to the HNP for one or more jobs and execute a few discrete
> functions:
>
> - find procs a
Ralph --
I'm a little confused as to what you're providing. In all 3 of the
scenarios you describe, you're saying that the external tool can
connect to the HNP for one or more jobs and execute a few discrete
functions:
- find procs and/or jobs running under that HNP
- querying status of
I should have also stated that one other difference in the "tool" setup is
that the tool does not create a session directory (you can override that if
you need one). This simplifies cleanup of the tool, and helps with tools
like orte-clean. Note that the session directory's main function is to hous
Hi Josh
I already converted orte-ps and orte-clean in the tmp/rhc-step2b branch on
OMPI's svn repository. Shouldn't be hard to convert the checkpoint/restart
tools to use it too - I may have already done some of that work, but I may
not be remembering it correctly.
I'll do some cleanup on the cod
Ralph,
This looks interesting. Can you point me to the header files and any
ORTE tools that you may have converted to use this library already
(e.g., orte-ps)? I can port the checkpoint/restart tools to this
library and start sending you some feedback on the API.
Cheers,
Josh
On Jan 16,
Hello all
Summary: this note provides a brief overview of how various tools can
interface to OMPI applications once the next version of ORTE is integrated
into the trunk. It includes a request for input regarding any needs (e.g.,
additional commands to be supported in the interface) that have not
