[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Configuration files may be sectioned. If, for example, you have a collection of programs that work closely together and, likely, have a common set of options, these programs may use a single, sectioned, configuration file. The file may be sectioned in either of two ways. The two ways may not be intermixed in a single configuration file. All text before the first segmentation line is processed, then only the segment that applies:
The file is partitioned by lines that contains an square open bracket
([
), the upper-cased c-variable-syntax program name
and a square close bracket (]
).
For example, if the prog-name
program had a sectioned
configuration file, then a line containing exactly ‘[PROG_NAME]’
would be processed.
The <?
marker indicates an XML directive.
The program
directive is interpreted by the configuration file
processor to segment the file in the same way as the ‘[PROG_NAME]’
sectioning is done. Any other XML directives are treated as comments.
Segmentation does not apply if the config file is being parsed with
the configFileLoad(3AutoOpts)
function.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This document was generated by Bruce Korb on June 25, 2010 using texi2html 1.82.