When a service station starts up, it reads three configuration files to determine which plugins should be started initially. The files are located in the config directory. They are used to store the default configuration, site-specific configuration, and host-specific configuration. Specifically, the files loaded are:
Each of the plugin configuration files loaded by the KSS has the same format. Each file is divided into sections, which have specified by lines that look a lot like RFC 822 headers. The RFC 822 quoting rules for the header values do not apply, but continuation lines are supported. Lines which start with a hash character "#" are comments and are ignored. Blank lines are also ignored. Section and value names are case-sensitive.
Sections are marked by lines containing a label in brackets; for example, the DEFAULTS section starts with the line:
[DEFAULTS]
Lines following the mark contain named values which are set for that section, until a new section is started or the end of the file.
Each section corresponds to a plugin. The DEFAULTS section provides default values for all sections.
Each section may contain variable definitions. See
below for a list of variable with defined
meanings. Some variables represent path or file names. Values
may refer to other variables by name using the Python formatting
operation `string %
dictionary
'. For example, to refer to the
`name
' value in the specification for
`args
', refer to it using the formatting syntax:
args: -n %(name)s more args...
See ``Fancier Output Formatting'' in the Python Tutorial for more information on the formatting operator.
When the plugin starter needs to find the value of a particular variable for a particular plugin, there are six places it can look. In order, they are:
Though only a small number of names are used to launch plugins when a KSS starts, those values may refer to values not among those used directly by the KSS. This allows additional values to be defined for use & override in the site- and host-specific files.
The following names are defined by the system and should not be overridden.
%(kosroot)s/plugins
. This is
the directory below which plugin implementations are
stored.