some language changes and fixes

      <dd>For some of the support scripts like <program>

      apxs</program> or <program>dbmmanage</program> (which are

      written in Perl) the Perl 5 interpreter is required (versions

      5.003 or newer are sufficient). If no such interpreter is found by

      the <program>configure</program> script there is no harm. Of course, you

      still can build and install Apache 2.0. Only those support scripts

      cannot be used. If you have multiple Perl interpreters

      installed (perhaps a Perl 4 from the vendor and a Perl 5 from

      your own), then it is recommended to use the <code>--with-perl</code>

      option (see below) to make sure the correct one is selected

      by <program>configure</program>.</dd>

      5.003 or newer are sufficient). If you have multiple Perl 

      interpreters (for example, a systemwide install of Perl 4, and 

      your own install of Perl 5), you are advised to use the 

      <code>--with-perl</code> option (see below) to make sure the 

      correct one is used by <program>configure</program>.

      If no Perl 5 interpreter is found by the 

      <program>configure</program> script, you will not be able to use 

      the affected support scripts. Of course, you will still be able to 

      build and use Apache 2.0.</dd>

    </dl>

</section>

    been created, then create enough to pick up the slack. Hence the

    code tries to maintain both the number of children appropriate for

    the current load on the server, and respect your wishes with the

    <directive>StartServers</directive> parameter.</p>

    <directive module="mpm_common">StartServers</directive> 

    parameter.</p>

    <p>Users of the <module>mod_status</module>

    <p>Users of <module>mod_status</module>

    will notice that the server statistics are <strong>not</strong>

    set to zero when a <code>USR1</code> is sent. The code was

    written to both minimize the time in which the server is unable

<section id="race"><title>Appendix: signals and race conditions</title>

    <p>Prior to Apache 1.2b9 there were several <em>race

    conditions</em> involving the restart and die signals (a simple

    description of race condition is: a time-sensitive problem, as

    in if something happens at just the wrong time it won't behave

    as expected). For those architectures that have the "right"

    conditions</em> involving the restart and die signals (a simply put, 

    a race condition is a time-sensitive problem - if something happens 

    at just the wrong time or things happen in the wrong order, 

    undesired behaviour will result. If the same thing happens at the right 

    time, all will be well). For those architectures that have the "right"

    feature set we have eliminated as many as we can. But it should

    be noted that there still do exist race conditions on certain

    be noted that race conditions do still exist on certain

    architectures.</p>

    <p>Architectures that use an on disk <directive

    module="mpm_common">ScoreBoardFile</directive> have the potential

    to corrupt their scoreboards. This can result in the "bind:

    <p>Architectures that use an on-disk <directive

    module="mpm_common">ScoreBoardFile</directive> can potentially have 

    their scoreboards corrupted. This can result in the "bind:

    Address already in use" (after <code>HUP</code>) or "long lost

    child came home!" (after <code>USR1</code>). The former is a fatal

    error, while the latter just causes the server to lose a

    scoreboard slot. So it might be advisable to use graceful

    scoreboard slot. So it may be advisable to use graceful

    restarts, with an occasional hard restart. These problems are very

    difficult to work around, but fortunately most architectures do

    not require a scoreboard file. See the <directive

    module="mpm_common">ScoreBoardFile</directive> documentation for a

    architecture uses it.</p>

    module="mpm_common">ScoreBoardFile</directive> documentation for

    architecture which uses it.</p>

    <p>All architectures have a small race condition in each child

    involving the second and subsequent requests on a persistent