ecFlow server environment variables control the execution of ecFlow and may be set before the start of the server, typically in a start-up script.
ecFlow will start happily without any of these variables being set , since all of them have a default value. These default values can be overridden by:
- Setting them in "server_environment.config". This file should then be placed in the current working directory , when invoking the server.
- Explicitly setting environment variables. These will override any setting in the "server_environment.config" file.
Table 4 2 ecFlow environment variables
...
Variablename
...
Explanation
...
Default value if variable not set
...
ECF_HOME
...
Home for all the ecFlow files, Different meaning for ecFlow itself and suites
...
Current working directory
...
ECF_PORT
...
Server port number
...
3141 (default but customisable)
...
ECF_JOB_CMD
...
Command to be executed to send a job
...
%ECF_JOB% 1> %ECF_JOBOUT% 2>&1
...
ECF_CHECK
...
Name of the checkpoint file
...
ecf.check
...
ECF_CHECKOLD
...
Name of the backup of the checkpoint file
...
ecf.check.b
...
ECF_LOG
...
History, or log file
...
ecf.log
...
ECF_CHECKINTERVAL
...
The interval to save the check point file in seconds. Avoid values <= 60 seconds
...
120
...
ECF_LISTS
...
ecFlow white-list file. Controls read write access to the server for each user
...
ecf.lists
...
ECF_SERVERS
...
ecFlow and CLI nickname table
...
/usr/local/lib/ecflowview/servers
...
For the full list of environment variables used the server please see 'ecflow_server' in the Glossary.