...
- cron is essentially restricted to "house cleaning" tasks, while it gets the task requeued as soon as it completes.No trigger can be expected from such task. It is used in operation to get nodes recording a day and time is achieved so they can alter a variable that that is used in a trigger in in a "user family". As an example, /admin/times is memorising that the milestone is achieved, and /mofc/thu/01/ref is the user family where a trigger is defined: that way we avoid cron dependency directly into the functional suite.
Center |
---|
![](/download/attachments/59018050/cron.png?version=1&modificationDate=1468933098267&api=v2)
Code Block |
---|
language | bash |
---|
title | admin suite definition |
---|
collapse | true |
---|
| suite admin
family times
family mon10
cron -w 1 10:00
task dummy
edit DELTA_DAY '-1'
edit YMD '20160717'
edit DOW '1'
endfamily
family mon22
label info "/mofc/mon products and plots"
cron -w 1 22:00
task dummy
edit DELTA_DAY '-1'
edit YMD '20160717'
edit LAST_YMD 21000101
edit LAST_HMS 9999
edit DOW '1'
endfamily
family thu10 # ...
endfamily
endsuite
suite user
family main
repeat YMD 19010101 20991201
task do
trigger /admin/times/mon22:LAST_YMD ge /user/main:YMD |
![](/download/attachments/59018050/cron_user.png?version=1&modificationDate=1468933098213&api=v2)
Code Block |
---|
node=/%SUITE%/%FAMILY%/%TASK%
%nopp
ecflow_client --alter change variable LAST_YMD "$(date +%Y%m%d)" $node
ecflow_client --alter change variable LAST_HMS "$(date +%H%M%S)" $node
%end |
|
Be careful that cron may prevent an inherited repeat attribute to loop as expected. We use it with a complete attribute when we have to (Acquisition task pattern).
...