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, if they want to do something when that happens.
I modified the way we were defining the subscriptions (in
orte/mca/rmgr/base/rmgr_base_stage_gate.c) to allow a caller to
define which standard triggers they wanted to know about. This
avoided overburdening the launch system and orterun with callbacks in
which they have no interest.
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 gate where it was occurring).
Given the availability of the new triggers, I changed that to conform
to his noted request.
Brian: please check that code to ensure I did this correctly.
As always, please let me know if you encounter any problems. I will
continue to test it myself as best I can.