18
Drizzle first reads all of the command line, as these options may also
19
include information about where configuration files should be found.
18
Drizzle first reads the command line options dealing with config file
19
location. These options may only be given as command line options.
20
Then, the config files are parsed, for all options. After that,
21
environment variables are processed, and any value given in them will
22
override values input from the config files. Finally, values on the command
23
line will be processed and any options given here take final precedence.
29
Command line options are of the form `--option-name=value`. There are some
30
boolean flags, such as `--help` which do not require (nor can accept) an
33
Environment variables are the same as the command line options, except that
34
the variable name is prefixed with *DRIZZLED_*, in all caps and all `.` and
35
`-` are turned into underscores. So the option
36
`--innodb.buffer_pool_size=10` could be given in the environment variable
37
*DRIZZLED_INNODB_BUFFER_POOL_SIZE*
39
The config files contain a set of lines of the form `option-name=value`, one
40
per line. Due to a bug in Boost.Program_options Boolean values require an argument, e.g. `console.enable=true`.
42
Config files support section headers such as `[innodb]` with all options
43
occuring subsequently being prefixed by the section header. For instance, if
50
It would be the same as::
52
innodb.buffer_pool_size=10M
added
removed
docs/configuration.rst
