Configuring the server

The ringserver program can be configured using either command line arguments or a configuration file. The most common options are available as command line arguments, all options can be set in a configuration file. All configuration file options are documented in the example configuration file that comes with the source code (doc/ring.conf) and in the man page (doc/ringserver.1).

Most configuration options can be changed on the fly. The server will monitor the configuration file for changes and apply them as needed, this reduces the amount of down-time and eases the maintenance of a ringserver node.

It is recommended to use a configuration file for production operation of a server. The advantages of using a configuration file are: more options available, use of dynamic options (options which can change during run time) and room for notes regarding the options.

Common configuration file options are described below.

RingDirectory - This is a directory where ringserver will store the internal ring buffer contents. Required, directory must be created.

DataLinkPort - Listen for DataLink connections on the specified port (16000 is the common DataLink port). Useful for querying and monitoring the server with, for example, dalitool.

SeedLinkPort - Listen for SeedLink connections on the specified port (18000 is the common SeedLink port).

ServerID - Server identification sent to clients, set appropriately.

TransferLogDirectory - Specify directory where transfer logs are to be written. By default they are written daily and both transmission and reception logs are written. This is optional, but if used the directory must be created.

MseedScan - Configure scanning of the /data/miniseed/ directory and sub-directories for Mini-SEED data. Use 'scan.state' as the statefile (created if necessary), allowing the server to be restarted without scanning duplicate data. Turn on the InitCurrentState option to avoid scanning current data when no StateFile is present.