Introduce mod_unixd into the documentation

    <p>This log will be opened as the user the child processes run

    as, <em>i.e.</em> the user specified in the main <directive

    module="mpm_common">User</directive> directive. This means that

    module="mod_unixd">User</directive> directive. This means that

    either the directory the script log is in needs to be writable

    by that user or the file needs to be manually created and set

    to be writable by that user. If you place the script log in

    </example>

    <p>The directory containing the lock database file must be

    writable by the <directive module="mpm_common">User</directive>

    and <directive module="mpm_common" >Group</directive> under which

    writable by the <directive module="mod_unixd">User</directive>

    and <directive module="mod_unixd" >Group</directive> under which

    Apache is running.</p>

    <p>You may wish to add a <directive module="core" type="section"

    <p>In order for <module>mod_dav</module> to manage files, it must

    be able to write to the directories and files under its control

    using the <directive module="mpm_common">User</directive> and

    <directive module="mpm_common">Group</directive> under which

    using the <directive module="mod_unixd">User</directive> and

    <directive module="mod_unixd">Group</directive> under which

    Apache is running.  New files created will also be owned by this

    <directive module="mpm_common">User</directive> and <directive

    module="mpm_common">Group</directive>.  For this reason, it is

    <directive module="mod_unixd">User</directive> and <directive

    module="mod_unixd">Group</directive>.  For this reason, it is

    important to control access to this account.  The DAV repository

    is considered private to Apache; modifying files outside of Apache

    (for example using FTP or filesystem-level tools) should not be

    </example>

    <p>The directory containing the lock database file must be

    writable by the <directive module="mpm_common">User</directive>

    and <directive module="mpm_common" >Group</directive> under which

    writable by the <directive module="mod_unixd">User</directive>

    and <directive module="mod_unixd" >Group</directive> under which

    Apache is running.  For security reasons, you should create a

    directory for this purpose rather than changing the permissions on

    an existing directory.  In the above example, Apache will create

    </example>

    <p>The directory containing the lock database file must be

    writable by the <directive module="mpm_common">User</directive>

    and <directive module="mpm_common" >Group</directive> under which

    writable by the <directive module="mod_unixd">User</directive>

    and <directive module="mod_unixd" >Group</directive> under which

    Apache is running.  For security reasons, you should create a

    directory for this purpose rather than changing the permissions on

    an existing directory.  In the above example, Apache will create

    <p>The <directive>SuexecUserGroup</directive> directive allows you

    to specify a user and group for CGI programs to run as. Non-CGI

    requests are still processes with the user specified in the <directive

    module="mpm_common">User</directive> directive. This directive replaces

    module="mod_unixd">User</directive> directive. This directive replaces

    the Apache 1.3 configuration of using the <code>User</code> and

    <code>Group</code> directives inside of VirtualHosts.</p>