That did the trick for me. Thanks!
Brian
On Feb 9, 2006, at 10:40 AM, Ralph H. Castain wrote:
Okay, it turned out that the counters were not being adjusted as
processes hit the INIT and LAUNCHED stages - just a case where that
hadn't been implemented yet. I've fixed that now (it was easier to
Okay, it turned out that the counters were not being adjusted as
processes hit the INIT and LAUNCHED stages - just a case where that
hadn't been implemented yet. I've fixed that now (it was easier to
fix than go back) and the wireup_stdin function is now being called.
Brian: can you verify tha
Hmmmyuck! I'll take a look - will set it back to what it was
before in the interim.
Thanks
Ralph
At 07:05 AM 2/9/2006, you wrote:
On Feb 8, 2006, at 12:46 PM, Ralph H. Castain wrote:
> In addition, I took advantage of the change to fix something Brian
> had flagged in the orte/mca/rmgr/ur
On Feb 8, 2006, at 12:46 PM, Ralph H. Castain wrote:
In addition, I took advantage of the change to fix something Brian
had flagged in the orte/mca/rmgr/urm/rmgr_urm.c file where he noted
that the wireup of stdin for io forwarding should occur at the LAUNCH
stage (as opposed to the STG1 stage ga
Hi all
As you'll see in my latest commit, I have made a slight modification
to the standard triggers that ensures we define them for ALL of the
process and job states. This will now allow users to subscribe to
triggers (for example) on all processes achieving INIT, LAUNCH, and
RUNNING states,
