...
Note: the ECFs are started in different directories so that the output and checkpoint files are not overwritten
Adding a new server to ecflowview adds the definition to the file ~/.ecflowview/servers. This can be modified directly.
You cannot start two ecFlow servers on the same machine with the same port number. To simplify users wanting their own ecFlow servers we have a script ecflow_start .sh(an example is included in the latest releases of ECF) that sets up an ecFlow server using a port number based on the users own unique user ID
You can check what port numbers are being used, with netstat: To list all open network ports on your machine, run netstat -lnptu.
Here is a breakdown of the parameters: •l
- l - List all listening ports
...
- n - Display the numeric IP addresses (i.e., don't do reverse DNS lookups
...
- p - List the process name that is attached to that port
...
- t - List all TCP connections
...
- u - List all UDP connections
Figure 7 1 Viewing new ECFLOW servers with ecflowview.
When using non-default ecFlow servers, ecflowview needs to be configured to recognise the port used. Opening the edit-preferences under ecflowview and selecting the servers tab you can describe your new ecFlow server to ecflowview.
Adding a new server to ecflowview adds the definition to the file ~/.xecfrc/servers. This can be modified directly.
It is a good idea to use a start up script that automatically sets up a unique port number.