occurring before a directive are ignored, so you may indent directives for clarity. The values of shell environment variables can be used in configuration file lines using the syntax ${ENVVAR}. If "ENVVAR" Wildcards and Regular Expressions The , , and directives can each use shell-style wildcard characters as in fnmatch from the C standard library. The character "*" matches any the piped log process is spawned using a shell. (usually with /bin/sh -c). Depending on the shell specifics invocation via shell might lead to an additional shell process for the lifetime of the logging

occurring before a directive are ignored, so you may indent directives for clarity. The values of shell environment variables can be used in configuration file lines using the syntax ${ENVVAR}. If "ENVVAR" Wildcards and Regular Expressions The , , and directives can each use shell-style wildcard characters as in fnmatch from the C standard library. The character "*" matches any the piped log process is spawned using a shell. (usually with /bin/sh -c). Depending on the shell specifics invocation via shell might lead to an additional shell process for the lifetime of the logging

is ignored, so you may indent directives for clarity. Blank lines are also ignored. The values of shell environment variables can be used in configuration file lines using the syntax ${ENVVAR}. If "ENVVAR" Wildcards and Regular Expressions The , , and directives can each use shell-style wildcard characters as in fnmatch from the C standard library. The character "*" matches any the piped log process is spawned using a shell. (usually with /bin/sh -c). Depending on the shell specifics invocation via shell might lead to an additional shell process for the lifetime of the logging

occurring before a directive are ignored, so you may indent directives for clarity. The values of shell environment variables can be used in configuration file lines using the syntax ${ENVVAR}. If "ENVVAR" Wildcards and Regular Expressions The , , and directives can each use shell-style wildcard characters as in fnmatch from the C standard library. The character "*" matches any the piped log process is spawned using a shell. (usually with /bin/sh -c). Depending on the shell specifics invocation via shell might lead to an additional shell process for the lifetime of the logging

is ignored, so you may indent directives for clarity. Blank lines are also ignored. The values of shell environment variables can be used in configuration file lines using the syntax ${ENVVAR}. If "ENVVAR" Wildcards and Regular Expressions The , , and directives can each use shell-style wildcard characters as in fnmatch from the C standard library. The character "*" matches any the piped log process is spawned using a shell. (usually with /bin/sh -c). Depending on the shell specifics invocation via shell might lead to an additional shell process for the lifetime of the logging

for clarity. Blank lines are also ignored. The values of variables defined with the Define of or shell environment variables can be used in configuration file lines using the syntax ${VAR}. If "VAR" is were found directly in the configuration file. Variables defined with Define take precedence over shell environment variables. If the "VAR" variable is not found, the characters ${VAR} are left unchanged Variable names may not contain colon ":" characters, to avoid clashes with RewriteMap's syntax. Only shell environment variables defined before the server is started can be used in expansions. Environment

for clarity. Blank lines are also ignored. The values of variables defined with the Define of or shell environment variables can be used in configuration file lines using the syntax ${VAR}. If "VAR" is were found directly in the configuration file. Variables defined with Define take precedence over shell environment variables. If the "VAR" variable is not found, the characters ${VAR} are left unchanged Variable names may not contain colon ":" characters, to avoid clashes with RewriteMap's syntax. Only shell environment variables defined before the server is started can be used in expansions. Environment

for clarity. Blank lines are also ignored. The values of variables defined with the Define of or shell environment variables can be used in configuration file lines using the syntax ${VAR}. If "VAR" is were found directly in the configuration file. Variables defined with Define take precedence over shell environment variables. If the "VAR" variable is not found, the characters ${VAR} are left unchanged Variable names may not contain colon ":" characters, to avoid clashes with RewriteMap's syntax. Only shell environment variables defined before the server is started can be used in expansions. Environment

so you may indent directives for clarity. The values of variables defined with the Define of or shell environment variables can be used in configuration file lines using the syntax ${VAR}. If "VAR" is were found directly in the configuration file. Variables defined with Define take precedence over shell environment variables. If the "VAR" variable is not found, the characters ${VAR} are left unchanged Variable names may not contain colon ":" characters, to avoid clashes with RewriteMap's syntax. Only shell environment variables defined before the server is started can be used in expansions. Environment

so you may indent directives for clarity. The values of variables defined with the Define of or shell environment variables can be used in configuration file lines using the syntax ${VAR}. If "VAR" is were found directly in the configuration file. Variables defined with Define take precedence over shell environment variables. If the "VAR" variable is not found, the characters ${VAR} are left unchanged Variable names may not contain colon ":" characters, to avoid clashes with RewriteMap's syntax. Only shell environment variables defined before the server is started can be used in expansions. Environment