File: run.rst

package info (click to toggle)
ecflow 5.15.2-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 51,868 kB
  • sloc: cpp: 269,341; python: 22,756; sh: 3,609; perl: 770; xml: 333; f90: 204; ansic: 141; makefile: 70
file content (66 lines) | stat: -rw-r--r-- 2,466 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66

.. _run_cli:

run
***







.. rubric:: Output of :code:`--help=run`



The following help text is generated by :code:`ecflow_client --help=run`

::

   
   run
   ---
   
   Ignore triggers, limits, time or date dependencies, just run the Task.
   When a job completes, it may be automatically re-queued if it has a cron
   or multiple time dependencies. If we have multiple time based attributes,
   then each run, will expire the time.
   When we run before the time, we want to avoid re-running the task then
   a flag is set, so that it is not automatically re-queued.
   A repeat attribute is incremented when all the child nodes are complete
   in this case the child nodes are automatically re-queued.
   Hence this command can be aid, in allowing a Repeat attribute to be incremented
     arg1 = (optional)force
            Forcibly run, even if there are nodes that are active or submitted
            This can result in zombie creation
     arg2 = node path(s). The paths must begin with a leading '/' character.
            If the path is /suite/family will recursively run all tasks
            When providing multiple paths avoid running the same task twice
   Example:
     --run=/suite/t1                    # run task t1
   Effect:
        task t1; time 12:00             # will complete if run manually
        task t2; time 10:00 13:00 01:00 # will run 4 times before completing
    When we have a time range(i.e as shown with task t2), then next time slot
    is incremented for each run, until it expires, and the task completes.
    Use the Why command, to show next run time (i.e. next time slot)
   
   The client considers, for both user and child commands, the following environment variables:
   
     ECF_HOST <string> [mandatory*]
       The main server hostname; default value is 'localhost'
     ECF_PORT <int> [mandatory*]
       The main server port; default value is '3141'
     ECF_SSL <any> [optional*]
       Enable secure communication between client and server.
     ECF_HOSTFILE <string> [optional]
       File that lists alternate hosts to try, if connection to main host fails
     ECF_HOSTFILE_POLICY <string> [optional]
       The policy ('task' or 'all') to define which commands consider using alternate hosts.
   
   The options marked with (*) must be specified in order for the client to communicate
   with the server, either by setting the environment variables or by specifying the
   command line options.