Seon Core environment variables

Environment variables are created and/or set by all Seon binaries, which values are based on the configuration of Seon. These variables are:

• Seon_CFGFILE: Seon main configuration file (absolute path information)
• Seon_IN_DIR: incoming data directory
• Seon_OUT_DIR: outgoing data directory
• Seon_TMP_DIR: temporary data directory
• Seon_BIN_DIR: binary program directory
• Seon_SCRIPT_DIR: script installation directory
• Seon_BACKUP_DIR: backup directory
• RAND_FILE: entropy file for OFTP2 needs
• OPENSSL_BIN: absolute path to openSSL binary
• RRDTOOL_BIN: absolute path to RRDtools binary
• RRDB_DATAPATH: RRD data path
• Seon_WEBGUI_DIR: web interface installation directory
• CA_FILE: configured absolute path to the root certificate file
• CA_PATH: configured absolute path to the root certificate directory

The following environment variables are extracted form the global Seon configuration file (default: /etc/seon.conf):

• Seon_DB_HOST
• Seon_DB_USER
• Seon_DB_PWD
• Seon_DB_NAME
• Seon_DB_SOCKET
• Seon_DB_PORT
• Seon_DB_TYPE: either "mysql", "DB2" or "sqlite3"

All processes started by Seon (event scripts, plugins, etc.) have access to these environment variables. The environment variable "Seon_CFGFILE" points to the absolute path to the Seon main configuration file. This has two effects:

• you may start Seon programs in a shell where this variable is set without using the parameter "-C" for all binaries (because the environment variable points to the correct position of the configfile)
• all subsequent processes started by Seon (like event scripts) don't have to bother about the given configfile (like plugins of Seon Enterprise).

Database performance benchmarking

Available in Seon 3 Core, an environment variable can be set to log all database access timing information into that given file:

Seon_DB_BENCHMARKLOG

You can set this variable to an absolute filename where Seon logs all innformation (example: "ksh" or "bash"):

export Seon_DB_BENCHMARKLOG=/tmp/db2perf.log

This file logs the connect and query time for every single database access, resulting in a fast growing file. The content if this file looks like this (using DB2 database abstraction layer, others like MySQL start with "MySQL"):

DB2 connect: 0.052482 seconds
DB2 SQL query: 0.126631 seconds
DB2 connect: 0.032447 seconds
DB2 SQL query: 0.004983 seconds
DB2 connect: 0.029555 seconds
DB2 SQL query: 0.004500 seconds
DB2 connect: 0.031012 seconds
DB2 SQL query: 0.001324 seconds