Difference between revisions of "OS4X Core environment variables"

From OS4X
Jump to navigation Jump to search
Line 1: Line 1:
Some environment variables are created and/or set by all OS4X binaries. These variables are:  
+
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:

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).