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 Apache children. In particular, this will control resources used by CGI scripts and SSI exec commands. The ThreadStackSize directive is used with some platforms to control the stack size. Modules

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 Apache children. In particular, this will control resources used by CGI scripts and SSI exec commands. The ThreadStackSize directive is used with some platforms to control the stack size. Modules

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 Apache children. In particular, this will control resources used by CGI scripts and SSI exec commands. The ThreadStackSize directive is used with some platforms to control the stack size. Modules

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 Apache children. In particular, this will control resources used by CGI scripts and SSI exec commands. The ThreadStackSize directive is used with some platforms to control the stack size. Modules

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 Apache children. In particular, this will control resources used by CGI scripts and SSI exec commands. The THREADSTACKSIZE directive is used only on Netware to control the stack size. 2.7. LOG FILES ServerRoot in /usr/local/apache then it is suggested that you create that directory as root, with commands like these: mkdir /usr/local/apache cd /usr/local/apache mkdir bin conf logs chown 0 . bin conf

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 Apache children. In particular, this will control resources used by CGI scripts and SSI exec commands. The ThreadStackSize directive is used with some platforms to control the stack size. Modules

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 Apache children. In particular, this will control resources used by CGI scripts and SSI exec commands. The THREADSTACKSIZE directive is used with some platforms to control the stack size. 44 CHAPTER

Unix platforms, piped logging commands configured using either ErrorLog or CustomLog were invoked using /bin/sh - c in 2.2 and earlier. In 2.4 and later, piped logging commands are executed directly. To 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

Unix platforms, piped logging commands configured using either ErrorLog or CustomLog were invoked using /bin/sh - c in 2.2 and earlier. In 2.4 and later, piped logging commands are executed directly. To restore 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

Unix platforms, piped logging commands configured using either ErrorLog or CustomLog were invoked using /bin/sh - c in 2.2 and earlier. In 2.4 and later, piped logging commands are executed directly. To restore 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