From 09c5fbaef3622012f45e705aebfc4b6ab6b09fb8 Mon Sep 17 00:00:00 2001 From: Markus Makela Date: Mon, 31 Aug 2015 11:33:10 +0300 Subject: [PATCH] Changed to PCRE for processing configuration file parameters. --- Getting-Started/Configuration-Guide.md | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/Getting-Started/Configuration-Guide.md b/Getting-Started/Configuration-Guide.md index 8077791ff..8e88eb9ef 100644 --- a/Getting-Started/Configuration-Guide.md +++ b/Getting-Started/Configuration-Guide.md @@ -33,7 +33,18 @@ The MaxScale configuration is read from a file which can be located in a number An explicit path to a configuration file can be passed by using the `-f` option to MaxScale. -The configuration file itself is based on the ".ini" file format and consists of various sections that are used to build the configuration, these sections define services, servers, listeners, monitors and global settings. +The configuration file itself is based on the ".ini" file format and consists of various sections that are used to build the configuration, these sections define services, servers, listeners, monitors and global settings. Parameters which expect a comma-separated list of values can be defined on multiple lines. The following is an example of a multi-line definition. + +``` +[MyService] +type=service +router=readconnroute +servers=server1, + server2, + server3 +``` + +The values of the parameter that are not on the first line need to have at least one whitespace character before them in order for them to be recognized as a part of the multi-line parameter. Please see the section about [Protocol Modules](#protocol-modules) for more details about MaxScale and the default directories where modules will be searched for.