18.2 Trigger Management |
|
18.2 Trigger Management |
|
A condensed listing of triggers can be viewed using the mdiag -T [<TRIGID>|<OBJECTID>] command. This will show all triggers to which the user has access, along with some basic information about the triggers. Specific triggers or all triggers attached to a specific object can be viewed by including the ID of the trigger or object.
Example
> mdiag -T > mdiag -T trigger.34 > mdiag -T job.493
Additional information can be obtained using the verbose mode of the mdiag -T -v [<TRIGID>|<OBJECTID>] command. As before, a subset can be obtained by specifying either a trigger or object ID.
Example
> mdiag -T -v > mdiag -T -v trigger.34 > mdiag -T -v job.493
The mdiag -T -V command is another viewing mode that provides additional state information about triggers, including reasons why triggers are currently blocked. This mode outputs information on a single line for each trigger, as opposed to the multiline output of the mdiag -T -v [<TRIGID>|<OBJECTID>] command. However, the mdiag -T -V command only operates in a global mode, showing all triggers available to the user.
Example
> mdiag -T -V
Triggers may be modified using the mschedctl -m trigger:<TRIGID> <ATTR>=<VAL> command.
Example
> mschedctl -m trigger:2 AType=exec,Offset=200,OID=system.1
In this example, Trigger 2's AType, Offset, and OID are changed to the new values shown.
Checkpointing is the process of saving state information when Moab is shut down.
In general, triggers defined in the moab.cfg file are not checkpointed. They are recreated when Moab restarts. The exception is the JOBCFG parameter, which attaches triggers to jobs as they are created. If a trigger defined in the moab.cfg file needs to be checkpointed because it was created at the command line (as opposed to in the configuration file), the checkpoint flag must be attached to the trigger. When creating a trigger using the mschedctl command, be sure to include the checkpoint flag.
Copyright © 2012 Adaptive Computing Enterprises, Inc.®