File: replace.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 (70 lines) | stat: -rw-r--r-- 2,651 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
67
68
69
70

.. _replace_cli:

replace
*******







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



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

::

   
   replace
   -------
   
   Replaces a node in the server, with the given path
   Can also be used to add nodes in the server
     arg1 = path to node
            must exist in the client defs(arg2). This is also the node we want to
            replace in the server
     arg2 = path to client definition file
            provides the definition of the new node
     arg3 = (optional) [ parent | false ] (default = parent)
            create parent families or suite as needed, when arg1 does not
            exist in the server
     arg4 = (optional) force (default = false) 
            Force the replacement even if it causes zombies to be created
   Replace can fail if:
   - The node path(arg1) does not exist in the provided client definition(arg2)
   - The client definition(arg2) must be free of errors
   - If the third argument is not provided, then node path(arg1) must exist in the server
   - Nodes to be replaced are in active/submitted state, in which case arg4(force) can be used
   
   Replace will preserve the suspended status, if this is not required please re-queue first
   After replace is done, we check trigger expressions. These are reported to standard output.
   It is up to the user to correct invalid trigger expressions, otherwise the tasks will *not* run.
   Please note, you can use --check to check trigger expression and limits in the server.
   For more information use --help check.
   
   Usage:
     --replace=/suite/f1/t1 /tmp/client.def  parent      # Add/replace node tree /suite/f1/t1
     --replace=/suite/f1/t1 /tmp/client.def  false force # replace t1 even if its active or submitted
   
   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.