(Click to open topic with navigation)
You can modify a trigger at any time by updating its settings in the Moab configuration file (moab.cfg). This will update most triggers at the beginning of the next Moab iteration; however, modifying template triggers (configured using RSVPROFILE or JOBCFG) will not update the instances of the trigger that were attached to individual reservations or jobs on creation. The modification will only affect the triggers that the template attaches to future objects.
Any trigger with a specified name can be modified using the mschedctl -m command in the following format:
mschedctl -m trigger: <triggerID><attr1>=<val1><attr2>=<val2>
Modifying triggers on the command line does not change their configuration in moab.cfg. Except for reservations that are checkpointed, changes made dynamically are lost when Moab restarts.
For example, the procedure below demonstrates how to modify the following trigger so that the offset is 10 minutes instead of 5 and so that Moab will attempt to fire the trigger up to 10 times if it fails. Assume your trigger currently looks like this:
NODECFG[DEFAULT] EType=fail,AType=exec,Action="/scripts/node_fail.pl",Name=nodeFailTrig,Offset=00:05:00,MultiFire=TRUE,RearmTime=01:00:00
To modify a trigger
> mschedctl -m trigger:nodeFailTrig
> mschedctl -m trigger:nodeFailTrig Offset=00:10:00 MaxRetry=10
The newly-specified attributes replace the original ones. Trigger nodeFailTrig now has an offset of 10 minutes and will try to fire a maximum of 10 times if it fails. The new trigger has the following attributes:
EType=fail,AType=exec,Action="/scripts/start_rsv.pl",Name=nodeFailTrig,Offset=00:10:00,MultiFire=TRUE,RearmTime=01:00:00,MaxRetry=10