Page History

Files Location

For a maintenable operational suite, we recommand to:

• start the server in a local /tmp directory (/:ECF_HOME)

• define ECF_FILES and ECF_INCLUDE variables, at suites and families level: scripts wrappers will be accessible for creation, and update under these directories.

• define /suite:ECF_HOME as another directory location, where jobs and related outputs will be found. These dynamic files may then be tar’ed as snapshot of the effective work associated to a suite/family, for later analysis or rerun.

• when server and remote jobs destination do not share a common directory for output-files, ECF_OUT variable needs to be present in the suite definition: it indicates the remote output path. In this situation, the suite designer is responsible to create the directory structure where the output file will be found. Most queueing system won’t start the job, if this directory is absent, and the task may remain visible as submitted, from the ecFlow server side.

• after seding the job complete command, the job may copy its output to ECF_NODE, to enable direct access from ecFlow server.

  When a file is requested from the ecflow-server, it is limited to 15k lines, to avoid the server spending too much time delivering very large output files.

  ecFlowview can be configured (globally, Edit-Preferences-Server-Option or locally top-node-menu->Options “Read Output an other files from disk when possible”) to get the best expected behaviour.

• use ecf.list file to restrict access to the server for read-write or read only access

  Code Block
  # 4.0.6 # ecflow_client --help reloadwsfile # ecflow_client --reloadwsfile # update ecflow server # $USER # rw access, aka $LOGNAME # -$USER # for read only access # export ECF_LISTS=/path/to/file # before server starts, to change location or name emos -rdx