location of your compiler, libraries, or header files. This is
done by passing either environment variables or command line
options to <program>configure</program>. For more information, see the
- <a href="programs/configure.html">configure manual page</a>.</p>
+ <program>configure</program> manual page.</p>
<p>For a short impression of what possibilities you have, here
is a typical example which compiles Apache for the installation
test for the availability of features on your system and build
Makefiles which will later be used to compile the server.</p>
- <p>Details on all the different <code>configure</code> options are
- available on the <a href="programs/configure.html">configure
- manual page</a>.</p>
+ <p>Details on all the different <program>configure</program> options are
+ available on the <program>configure</program> manual page.</p>
</section>
<section id="compile"><title>Build</title>
limits the scope of the enclosed directives by URL. It is similar to the
<directive type="section" module="core">Directory</directive>
directive, and starts a subsection which is terminated with a
- <code></Location></code> directive. <directive
+ <code></Location></code> directive. <directive
type="section">Location</directive> sections are processed in the
order they appear in the configuration file, after the <directive
type="section" module="core">Directory</directive> sections and
multi-process multi-threaded server. By using threads to serve
requests, it is able to serve a large number of requests with
less system resources than a process-based server. Yet it
- retains much of the stability of a process-based server by
+ retains much of the stability of a process-based server by
keeping multiple processes available, each with many threads.</p>
<p>The most important directives used to control this MPM are
controls how frequently the server recycles processes by killing
old ones and launching new ones.</p>
</section>
-
+
<directivesynopsis location="mpm_common"><name>AcceptMutex</name>
</directivesynopsis>
<directivesynopsis location="mpm_common"><name>CoreDumpDirectory</name>
libraries integrated. Otherwise the support binaries are linked
dynamically by default.</dd>
- <dt><code>--enable-suexec</code></dt>
+ <dt><code>--enable-suexec</code></dt>
<dd>Use this option to enable <program>
suexec</program>, which allows you to set
uid and gid for spawned processes. <strong>Do not use this
<p>This configuration will rotate the logfile whenever it reaches
a size of 5 megabytes.</p>
-
+
<example>
ErrorLog "|bin/rotatelogs /var/logs/errorlog.%Y-%m-%d-%H_%M_%S 5M"
</example>
different IP address for every web site, or "<a
href="name-based.html">name-based</a>", meaning that you have
multiple names running on each IP address. The fact that they
- are running on the same physical server is not apparent to the
+ are running on the same physical server is not apparent to the
end user.</p>
<p>Apache was one of the first servers to support IP-based