Difference between revisions of "OS4X Core environment variables"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| − | + | Environment variables are created and/or set by all OS4X binaries, which values are based on the configuration of OS4X. These variables are: | |
*<code>OS4X_CFGFILE</code>: [[OS4X_Core_installation#Main_configuration|OS4X main configuration file (absolute path information)]] | *<code>OS4X_CFGFILE</code>: [[OS4X_Core_installation#Main_configuration|OS4X main configuration file (absolute path information)]] | ||
*<code>OS4X_IN_DIR</code>: [[OS4X_Core_configuration#data_incoming_directory|incoming data directory]] | *<code>OS4X_IN_DIR</code>: [[OS4X_Core_configuration#data_incoming_directory|incoming data directory]] | ||
Revision as of 17:54, 6 February 2010
Environment variables are created and/or set by all OS4X binaries, which values are based on the configuration of OS4X. These variables are:
OS4X_CFGFILE: OS4X main configuration file (absolute path information)OS4X_IN_DIR: incoming data directoryOS4X_OUT_DIR: outgoing data directoryOS4X_TMP_DIR: temporary data directoryOS4X_BIN_DIR: binary program directoryOS4X_SCRIPT_DIR: script installation directoryOS4X_BACKUP_DIR: backup directoryRAND_FILE: entropy file for OFTP2 needsOPENSSL_BIN: absolute path to openSSL binaryRRDTOOL_BIN: absolute path to RRDtools binaryRRDB_DATAPATH: RRD data pathOS4X_WEBGUI_DIR: web interface installation directoryJAVA_BIN: configured path to the Java runtime (JRE) binaryCA_FILE: configured absolute path to the root certificate fileCA_PATH: configured absolute path to the root certificate directory
All processes started by OS4X (event scripts, plugins, etc.) have access to these environment variables.
The environment variable "OS4X_CFGFILE" points to the absolute path to the OS4X main configuration file. This has two effects:
- you may start OS4X 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 OS4X (like event scripts) don't have to bother about the given configfile (like plugins of OS4X Enterprise).