From: Joshua Slive Date: Thu, 25 Mar 2004 19:16:24 +0000 (+0000) Subject: Intergrate Kess' configure docs in the docs tree and, X-Git-Tag: pre_ajp_proxy~453 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=f4887a358b28c70dcf9ab76e490f72118fb76d68;p=apache Intergrate Kess' configure docs in the docs tree and, in particular, integrate them into install.xml by removing large chunks of that document and making it a summary with pointers into configure.xml. (I also snuck in the odd fix to both install.xml and configure.xml. Sorry for the mix.) git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@103154 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/install.html.en b/docs/manual/install.html.en index 4301558df6..8ba67911b6 100644 --- a/docs/manual/install.html.en +++ b/docs/manual/install.html.en @@ -52,7 +52,7 @@
  • Customize
  • Test
  • Upgrading
    • -

    See also

    +

    See also

    top

    Overview for the @@ -167,54 +167,20 @@

    Download

    Apache can be downloaded from the Apache HTTP Server - download site which lists several mirrors. You'll find here - the latest stable release.

    - -

    After downloading, especially if a mirror site is used, it - is important to verify that you have a complete and unmodified - version of the Apache HTTP Server. This can be accomplished by - testing the downloaded tarball against the PGP signature. This, - in turn, is a two step procedure. First, you must obtain the - KEYS - file from the Apache distribution site, too. (To assure that the - KEYS file itself has not been modified, it may be a good - idea to use a file from a previous distribution of Apache or import - the keys from a public key server.) The keys are imported into - your personal key ring using one of the following commands (depending - on your pgp version):

    - -

    $ pgp < KEYS

    - -

    or

    - -

    $ gpg --import KEYS

    - -

    The next step is to test the tarball against the PGP - signature, which should always be obtained from the main Apache - website. A link to the signature file is placed behind the - corresponding download link or may be found in the particular - directory at the Apache - distribution site. Its filename is identical to the source - tarball with the addition of .asc. Then you can check - the distribution with one of the following commands (again, - depending on your pgp version):

    - -

    $ pgp httpd-2_1_NN.tar.gz.asc

    - -

    or

    - -

    $ gpg --verify httpd-2_1_NN.tar.gz.asc

    - -

    You should receive a message like

    - -

    Good signature from user "Martin Kraemer - <martin@apache.org>".

    - -

    Depending on the trust relationships contained in your key - ring, you may also receive a message saying that the - relationship between the key and the signer of the key cannot - be verified. This is not a problem if you trust the - authenticity of the KEYS file.

    + download site which lists several mirrors. Most users of + Apache on unix-like systems will be better off downloading and + compiling a source version. The build process (described below) is + easy, and it allows you to customize your server to suit your needs. + In addition, binary releases are often not up to date with the latest + source releases. If you do download a binary, follow the instructions + in the INSTALL.bindist file inside the distribution.

    + +

    After downloading, it is important to verify that you ahve a + complete and unmodified version of the Apache HTTP Server. This + can be accomplished by testing the downloaded tarball against the + PGP signature. Details on how to do this are available on the download + page and an extended example is available describing the use of + PGP.

    top
    @@ -224,8 +190,8 @@ simple matter of uncompressing, and then untarring:

    - $ gzip -d httpd-2_1_NN.tar.gz
    - $ tar xvf httpd-2_1_NN.tar +$ gzip -d httpd-2_1_NN.tar.gz
    +$ tar xvf httpd-2_1_NN.tar

    This will create a new directory under the current directory @@ -236,26 +202,47 @@

    Configuring the source tree

    -

    The next step is to configure the Apache source tree for - your particular platform and personal requirements. This is - done using the script configure included in the - root directory of the distribution. (Developers downloading the - CVS version of the Apache source tree will need to have - autoconf and libtool installed and - will need to run buildconf before proceeding with - the next steps. This is not necessary for official - releases.)

    +

    The next step is to configure the Apache source tree for your + particular platform and personal requirements. This is done using + the script configure included in + the root directory of the distribution. (Developers downloading + the CVS version of the Apache source tree will need to have + autoconf and libtool installed and will + need to run buildconf before proceeding with the next + steps. This is not necessary for official releases.)

    To configure the source tree using all the default options, simply type ./configure. To change the default options, configure accepts a variety of variables - and command line options. Environment variables are generally - placed before the ./configure command, while other - options are placed after. The most important option here is the - location prefix where Apache is to be installed later, because - Apache has to be configured for this location to work - correctly. But there are a lot of other options available for - your pleasure.

    + and command line options.

    + +

    The most important option is the location prefix where Apache + is to be installed later, because Apache has to be configured for + this location to work correctly. More fine-tuned control of the + location of files is possible with additional configure + options.

    + +

    Also at this point, you can specify which features you + want included in Apache by enabling and disabling modules. Apache comes with a Base set of modules included by + default. Other modules are enabled using the + enable-module option, where + module is the name of the module with the + mod_ string removed and with any underscore converted + to a dash. You can also choose to compile modules as shared objects (DSOs) -- which can be loaded + or unloaded at runtime -- by using the option + enable-module=shared. Similarly, you can + disable Base modules with the + --disable-module option. Be careful when + using these options, since configure cannot warn you + if the module you specify does not exit; it will simply ignore the + option.

    + +

    In addition, it is sometimes necessary to provide the + configure script with extra information about the + location of your compiler, libraries, or header files. This is + done by passing either environment variables or command line + options to configure. For more information, see the + configure manual page.

    For a short impression of what possibilities you have, here is a typical example which compiles Apache for the installation @@ -275,278 +262,9 @@ test for the availability of features on your system and build Makefiles which will later be used to compile the server.

    -

    The easiest way to find all of the configuration flags for - Apache is to run ./configure --help. What follows is a - brief description of most of the arguments and environment - variables.

    - -

    Environment Variables

    - -

    The autoconf build process uses several environment - variables to configure the build environment. In general, these - variables change the method used to build Apache, but not the - eventual features of the server. These variables can be placed - in the environment before invoking configure, but - it is usually easier to specify them on the - configure command line as demonstrated in the - example above.

    - -
    -
    CC=...
    - -
    The name of the C compiler command.
    - -
    CPPFLAGS=...
    - -
    Miscellaneous C preprocessor and compiler options.
    - -
    CFLAGS=...
    - -
    Debugging and optimization options for the C - compiler.
    - -
    LDFLAGS=...
    - -
    Miscellaneous options to be passed to the linker.
    - -
    LIBS=...
    - -
    Library location information ("-L" and - "-l" options) to pass to the linker.
    - -
    INCLUDES=...
    - -
    Header file search directories ("-Idir").
    - -
    TARGET=... [Default: httpd]
    - -
    Name of the executable which will be built.
    - -
    NOTEST_CPPFLAGS=...
    - -
    NOTEST_CFLAGS=...
    - -
    NOTEST_LDFLAGS=...
    - -
    NOTEST_LIBS=...
    - -
    These variables share the same function as their - non-NOTEST namesakes. However, the variables are - applied to the build process only after autoconf has performed its - feature testing. This allows the inclusion of flags which - will cause problems during feature testing, but must be used - for the final compilation.
    - -
    SHLIB_PATH=...
    - -
    Options which specify shared library paths for the - compiler and linker.
    -
    - - -

    autoconf Output Options

    - -
    -
    --help
    - -
    Prints the usage message including all available options, - but does not actually configure anything.
    - -
    --quiet
    - -
    Prevents the printing of the usual "checking..." - messages.
    - -
    --verbose
    - -
    Prints much more information during the configuration - process, including the names of all the files examined.
    -
    - - -

    Pathnames

    - -

    There are currently two ways to configure the pathnames - under which Apache will install its files. First, you can - specify a directory and have Apache install itself under that - directory in its default locations.

    - -
    -
    --prefix=PREFIX [Default: - /usr/local/apache2]
    - -
    Specifies the directory under which the Apache files will - be installed.
    -
    - -

    It is possible to specify that architecture-dependent files - should be placed under a different directory.

    - -
    -
    --exec-prefix=EPREFIX [Default: - PREFIX]
    - -
    Specifies the directory under which - architecture-dependent files will be placed.
    -
    - -

    The second, and more flexible way to configure the install - path locations for Apache is using the - config.layout file. Using this method, it is - possible to separately specify the location for each type of - file within the Apache installation. The - config.layout file contains several example - configurations, and you can also create your own custom - configuration following the examples. The different layouts in - this file are grouped into <Layout - FOO>...</Layout> sections and referred to by - name as in FOO.

    - -
    -
    --enable-layout=LAYOUT
    - -
    Use the named layout in the config.layout - file to specify the installation paths.
    -
    - - - -

    Modules

    - -

    Apache is a modular server. Only the most basic - functionality is included in the core server. Extended features - are available in various modules. During the configuration - process, you must select which modules to compile for use with - your server. You can view a list of modules included in - the documentation. Those modules with a status of "Base" are - included by default and must be specifically disabled if you do - not want them (e.g. mod_userdir). Modules with any - other status must be specifically enabled if you wish to use them - (e.g. mod_expires).

    - -

    There are two ways for a module to be compiled and used with - Apache. Modules may be statically compiled, which - means that they are permanently included in the Apache binary. - Alternatively, if your operating system supports Dynamic Shared - Objects (DSOs) and autoconf can detect that support, then - modules may be dynamically compiled. DSO modules are - stored separately from the Apache binary, and may be included - or excluded from the server using the run-time configuration - directives provided by mod_so. - The mod_so is automatically included in the server if any - dynamic modules are included in the compilation. If you would - like to make your server capable of loading DSOs without - actually compiling any dynamic modules, you can explicitly - --enable-so.

    - -
    -
    --enable-MODULE[=shared]
    - -
    Compile and include the module MODULE. The - identifier MODULE is the Module - Identifier from the module documentation without the - "_module" string. To compile the module as a DSO, add the - option =shared.
    - -
    --disable-MODULE
    - -
    Remove the module MODULE which would otherwise - be compiled and included.
    - -
    --enable-modules=MODULE-LIST
    - -
    Compile and include the modules listed in the - space-separated MODULE-LIST.
    - -
    - --enable-mods-shared=MODULE-LIST
    - -
    Compile and include the modules in the space-separated - MODULE-LIST as dynamically loadable (DSO) - modules.
    -
    - -

    The MODULE-LIST in the - --enable-modules and - --enable-mods-shared options is usually a - space-separated list of module identifiers. For example, to - enable mod_dav and mod_info, - you can either use

    - -

    ./configure --enable-dav --enable-info

    - -

    or, equivalently,

    - -

    ./configure --enable-modules="dav info"

    - -

    In addition, the special keywords all or - most can be used to add all or most of the modules - in one step. You can then remove any modules that you do not - want with the --disable-MODULE option. - For example, to include all modules as DSOs with the exception - of mod_info, you can use

    - -

    - ./configure --enable-mods-shared=all - --disable-info -

    - -

    In addition to the standard set of modules, Apache 2.0 also - includes a choice of Multi-Processing - Modules (MPMs). One, and only one MPM must be included in - the compilation process. The default MPMs for each platform are - listed on the MPM documentation page, - but can be overridden on the configure command - line.

    - -
    -
    --with-mpm=NAME
    - -
    Choose the mpm NAME.
    -
    - -

    To activate an MPM called mpm_name, you can use

    - -

    - ./configure --with-mpm=mpm_name -

    - - - -

    DBM

    - -

    Several Apache features, including - mod_authn_dbm and mod_rewrite's - DBM RewriteMap use - simple key/value databases for quick lookups of information. Apache - includes SDBM with its source-code, so this database is always - available. If you would like to use other database types, the - following configure options are available:

    - -
    -
    --with-gdbm[=path]
    -
    --with-ndbm[=path]
    -
    --with-berkeley-db[=path]
    - -
    If no path is specified, Apache will search for the -include files and libraries in the usual search paths. An explicit -path will cause Apache to look in -path/lib and -path/include for the relevant files. Finally, -the path may specify specific include and library paths -separated by a colon.
    -
    - - - -

    Suexec

    - -

    Apache includes a support program called suexec which can be used to isolate user - CGI programs. However, if suexec is improperly configured, it - can cause serious security problems. Therefore, you should - carefully read and consider the suexec - documentation before implementing this feature.

    - +

    Details on all the different configure options are + available on the configure + manual page.

    top

    Build

    diff --git a/docs/manual/install.xml b/docs/manual/install.xml index 664df12ae0..bb84a123cc 100644 --- a/docs/manual/install.xml +++ b/docs/manual/install.xml @@ -44,6 +44,7 @@ +Configure the source tree Starting Apache Stopping and Restarting @@ -165,55 +166,22 @@

    Apache can be downloaded from the Apache HTTP Server - download site which lists several mirrors. You'll find here - the latest stable release.

    - -

    After downloading, especially if a mirror site is used, it - is important to verify that you have a complete and unmodified - version of the Apache HTTP Server. This can be accomplished by - testing the downloaded tarball against the PGP signature. This, - in turn, is a two step procedure. First, you must obtain the - KEYS - file from the Apache distribution site, too. (To assure that the - KEYS file itself has not been modified, it may be a good - idea to use a file from a previous distribution of Apache or import - the keys from a public key server.) The keys are imported into - your personal key ring using one of the following commands (depending - on your pgp version):

    - -$ pgp < KEYS - -

    or

    - -$ gpg --import KEYS - -

    The next step is to test the tarball against the PGP - signature, which should always be obtained from the main Apache - website. A link to the signature file is placed behind the - corresponding download link or may be found in the particular - directory at the Apache - distribution site. Its filename is identical to the source - tarball with the addition of .asc. Then you can check - the distribution with one of the following commands (again, - depending on your pgp version):

    - -$ pgp httpd-2_1_NN.tar.gz.asc - -

    or

    - -$ gpg --verify httpd-2_1_NN.tar.gz.asc - -

    You should receive a message like

    - -Good signature from user "Martin Kraemer - <martin@apache.org>". - -

    Depending on the trust relationships contained in your key - ring, you may also receive a message saying that the - relationship between the key and the signer of the key cannot - be verified. This is not a problem if you trust the - authenticity of the KEYS file.

    + download site which lists several mirrors. Most users of + Apache on unix-like systems will be better off downloading and + compiling a source version. The build process (described below) is + easy, and it allows you to customize your server to suit your needs. + In addition, binary releases are often not up to date with the latest + source releases. If you do download a binary, follow the instructions + in the INSTALL.bindist file inside the distribution.

    + +

    After downloading, it is important to verify that you ahve a + complete and unmodified version of the Apache HTTP Server. This + can be accomplished by testing the downloaded tarball against the + PGP signature. Details on how to do this are available on the download + page and an extended example is available describing the use of + PGP.

    @@ -223,8 +191,8 @@ simple matter of uncompressing, and then untarring:

    - $ gzip -d httpd-2_1_NN.tar.gz
    - $ tar xvf httpd-2_1_NN.tar +$ gzip -d httpd-2_1_NN.tar.gz
    +$ tar xvf httpd-2_1_NN.tar

    This will create a new directory under the current directory @@ -235,26 +203,53 @@

    Configuring the source tree -

    The next step is to configure the Apache source tree for - your particular platform and personal requirements. This is - done using the script configure included in the - root directory of the distribution. (Developers downloading the - CVS version of the Apache source tree will need to have - autoconf and libtool installed and - will need to run buildconf before proceeding with - the next steps. This is not necessary for official - releases.)

    +

    The next step is to configure the Apache source tree for your + particular platform and personal requirements. This is done using + the script configure included in + the root directory of the distribution. (Developers downloading + the CVS version of the Apache source tree will need to have + autoconf and libtool installed and will + need to run buildconf before proceeding with the next + steps. This is not necessary for official releases.)

    To configure the source tree using all the default options, simply type ./configure. To change the default options, configure accepts a variety of variables - and command line options. Environment variables are generally - placed before the ./configure command, while other - options are placed after. The most important option here is the - location prefix where Apache is to be installed later, because - Apache has to be configured for this location to work - correctly. But there are a lot of other options available for - your pleasure.

    + and command line options.

    + +

    The most important option is the location prefix where Apache + is to be installed later, because Apache has to be configured for + this location to work correctly. More fine-tuned control of the + location of files is possible with additional configure + options.

    + +

    Also at this point, you can specify which features you + want included in Apache by enabling and disabling modules. Apache comes with a Base set of modules included by + default. Other modules are enabled using the + enable-module option, where + module is the name of the module with the + mod_ string removed and with any underscore converted + to a dash. You can also choose to compile modules as shared objects (DSOs) -- which can be loaded + or unloaded at runtime -- by using the option + enable-module=shared. Similarly, you can + disable Base modules with the + --disable-module option. Be careful when + using these options, since configure cannot warn you + if the module you specify does not exit; it will simply ignore the + option.

    + +

    In addition, it is sometimes necessary to provide the + configure script with extra information about the + location of your compiler, libraries, or header files. This is + done by passing either environment variables or command line + options to configure. For more information, see the + configure manual page.

    For a short impression of what possibilities you have, here is a typical example which compiles Apache for the installation @@ -274,282 +269,9 @@ test for the availability of features on your system and build Makefiles which will later be used to compile the server.

    -

    The easiest way to find all of the configuration flags for - Apache is to run ./configure --help. What follows is a - brief description of most of the arguments and environment - variables.

    - -
    Environment Variables - -

    The autoconf build process uses several environment - variables to configure the build environment. In general, these - variables change the method used to build Apache, but not the - eventual features of the server. These variables can be placed - in the environment before invoking configure, but - it is usually easier to specify them on the - configure command line as demonstrated in the - example above.

    - -
    -
    CC=...
    - -
    The name of the C compiler command.
    - -
    CPPFLAGS=...
    - -
    Miscellaneous C preprocessor and compiler options.
    - -
    CFLAGS=...
    - -
    Debugging and optimization options for the C - compiler.
    - -
    LDFLAGS=...
    - -
    Miscellaneous options to be passed to the linker.
    - -
    LIBS=...
    - -
    Library location information ("-L" and - "-l" options) to pass to the linker.
    - -
    INCLUDES=...
    - -
    Header file search directories ("-Idir").
    - -
    TARGET=... [Default: httpd]
    - -
    Name of the executable which will be built.
    - -
    NOTEST_CPPFLAGS=...
    - -
    NOTEST_CFLAGS=...
    - -
    NOTEST_LDFLAGS=...
    - -
    NOTEST_LIBS=...
    - -
    These variables share the same function as their - non-NOTEST namesakes. However, the variables are - applied to the build process only after autoconf has performed its - feature testing. This allows the inclusion of flags which - will cause problems during feature testing, but must be used - for the final compilation.
    - -
    SHLIB_PATH=...
    - -
    Options which specify shared library paths for the - compiler and linker.
    -
    -
    - -
    autoconf Output Options - -
    -
    --help
    - -
    Prints the usage message including all available options, - but does not actually configure anything.
    - -
    --quiet
    - -
    Prevents the printing of the usual "checking..." - messages.
    - -
    --verbose
    - -
    Prints much more information during the configuration - process, including the names of all the files examined.
    -
    -
    - -
    Pathnames - -

    There are currently two ways to configure the pathnames - under which Apache will install its files. First, you can - specify a directory and have Apache install itself under that - directory in its default locations.

    - -
    -
    --prefix=PREFIX [Default: - /usr/local/apache2]
    - -
    Specifies the directory under which the Apache files will - be installed.
    -
    - -

    It is possible to specify that architecture-dependent files - should be placed under a different directory.

    - -
    -
    --exec-prefix=EPREFIX [Default: - PREFIX]
    - -
    Specifies the directory under which - architecture-dependent files will be placed.
    -
    - -

    The second, and more flexible way to configure the install - path locations for Apache is using the - config.layout file. Using this method, it is - possible to separately specify the location for each type of - file within the Apache installation. The - config.layout file contains several example - configurations, and you can also create your own custom - configuration following the examples. The different layouts in - this file are grouped into <Layout - FOO>...</Layout> sections and referred to by - name as in FOO.

    - -
    -
    --enable-layout=LAYOUT
    - -
    Use the named layout in the config.layout - file to specify the installation paths.
    -
    - -
    - -
    Modules - -

    Apache is a modular server. Only the most basic - functionality is included in the core server. Extended features - are available in various modules. During the configuration - process, you must select which modules to compile for use with - your server. You can view a list of modules included in - the documentation. Those modules with a status of "Base" are - included by default and must be specifically disabled if you do - not want them (e.g. mod_userdir). Modules with any - other status must be specifically enabled if you wish to use them - (e.g. mod_expires).

    - -

    There are two ways for a module to be compiled and used with - Apache. Modules may be statically compiled, which - means that they are permanently included in the Apache binary. - Alternatively, if your operating system supports Dynamic Shared - Objects (DSOs) and autoconf can detect that support, then - modules may be dynamically compiled. DSO modules are - stored separately from the Apache binary, and may be included - or excluded from the server using the run-time configuration - directives provided by mod_so. - The mod_so is automatically included in the server if any - dynamic modules are included in the compilation. If you would - like to make your server capable of loading DSOs without - actually compiling any dynamic modules, you can explicitly - --enable-so.

    - -
    -
    --enable-MODULE[=shared]
    - -
    Compile and include the module MODULE. The - identifier MODULE is the Module - Identifier from the module documentation without the - "_module" string. To compile the module as a DSO, add the - option =shared.
    - -
    --disable-MODULE
    - -
    Remove the module MODULE which would otherwise - be compiled and included.
    - -
    --enable-modules=MODULE-LIST
    - -
    Compile and include the modules listed in the - space-separated MODULE-LIST.
    - -
    - --enable-mods-shared=MODULE-LIST
    - -
    Compile and include the modules in the space-separated - MODULE-LIST as dynamically loadable (DSO) - modules.
    -
    - -

    The MODULE-LIST in the - --enable-modules and - --enable-mods-shared options is usually a - space-separated list of module identifiers. For example, to - enable mod_dav and mod_info, - you can either use

    - -./configure --enable-dav --enable-info - -

    or, equivalently,

    - -./configure --enable-modules="dav info" - -

    In addition, the special keywords all or - most can be used to add all or most of the modules - in one step. You can then remove any modules that you do not - want with the --disable-MODULE option. - For example, to include all modules as DSOs with the exception - of mod_info, you can use

    - - - ./configure --enable-mods-shared=all - --disable-info - - -

    In addition to the standard set of modules, Apache 2.0 also - includes a choice of Multi-Processing - Modules (MPMs). One, and only one MPM must be included in - the compilation process. The default MPMs for each platform are - listed on the MPM documentation page, - but can be overridden on the configure command - line.

    - -
    -
    --with-mpm=NAME
    - -
    Choose the mpm NAME.
    -
    - -

    To activate an MPM called mpm_name, you can use

    - - - ./configure --with-mpm=mpm_name - - -
    - -
    DBM - -

    Several Apache features, including - mod_authn_dbm and mod_rewrite's - DBM RewriteMap use - simple key/value databases for quick lookups of information. Apache - includes SDBM with its source-code, so this database is always - available. If you would like to use other database types, the - following configure options are available:

    - -
    -
    --with-gdbm[=path]
    -
    --with-ndbm[=path]
    -
    --with-berkeley-db[=path]
    - -
    If no path is specified, Apache will search for the -include files and libraries in the usual search paths. An explicit -path will cause Apache to look in -path/lib and -path/include for the relevant files. Finally, -the path may specify specific include and library paths -separated by a colon.
    -
    -
    - - -
    Suexec - -

    Apache includes a support program called suexec which can be used to isolate user - CGI programs. However, if suexec is improperly configured, it - can cause serious security problems. Therefore, you should - carefully read and consider the suexec - documentation before implementing this feature.

    -
    +

    Details on all the different configure options are + available on the configure + manual page.

    Build diff --git a/docs/manual/programs/configure.html.en b/docs/manual/programs/configure.html.en index b9953fa80c..b0808b333f 100644 --- a/docs/manual/programs/configure.html.en +++ b/docs/manual/programs/configure.html.en @@ -26,10 +26,9 @@ particular platform. Various options allow the compilation of a server corresponding to your personal requirements.

    -

    This script, included in the root directory of the distribution, - is for compilation on Unix and Unix-like systems only. For other - platforms, see the platform - documentation.

    +

    This script, included in the root directory of the source + distribution, is for compilation on Unix and Unix-like systems + only. For other platforms, see the platform documentation.

    • Synopsis
    • Options
      • @@ -789,11 +788,12 @@ libraries integrated. Otherwise the support binaries are linked dynamically by default. -
      --enable-suexec
      -
      Use this option to enable suexec, which allows you to set uid - and gid for spawned processes. Further options to configure - suexec are described below.
      - +
      --enable-suexec
      +
      Use this option to enable suexec, which allows you to set + uid and gid for spawned processes. Do not use this + option unless you understand all the security implications of + running a suid binary on your server. Further options + to configure suexec are described below.

      It is possible to create a statically linked binary of a single support program by using the following options:

      diff --git a/docs/manual/programs/configure.xml b/docs/manual/programs/configure.xml index 4b2ec990c6..e449609f84 100644 --- a/docs/manual/programs/configure.xml +++ b/docs/manual/programs/configure.xml @@ -29,10 +29,10 @@ particular platform. Various options allow the compilation of a server corresponding to your personal requirements.

      -

      This script, included in the root directory of the distribution, - is for compilation on Unix and Unix-like systems only. For other - platforms, see the platform - documentation.

      +

      This script, included in the root directory of the source + distribution, is for compilation on Unix and Unix-like systems + only. For other platforms, see the platform documentation.

      Compiling and Installing @@ -795,12 +795,14 @@ libraries integrated. Otherwise the support binaries are linked dynamically by default. -
      --enable-suexec
      +
      --enable-suexec
      Use this option to enable suexec, which allows you to set uid - and gid for spawned processes. Further options to configure - suexec are described below.
      - + href="suexec.html">suexec, which allows you to set + uid and gid for spawned processes. Do not use this + option unless you understand all the security implications of + running a suid binary on your server. Further options + to configure suexec are described below.

      It is possible to create a statically linked binary of a single support program by using the following options:

      diff --git a/docs/manual/programs/index.html.en b/docs/manual/programs/index.html.en index b14b6a569f..261e593a97 100644 --- a/docs/manual/programs/index.html.en +++ b/docs/manual/programs/index.html.en @@ -45,6 +45,10 @@
      APache eXtenSion tool
      +
      configure
      + +
      Configure the source tree
      +
      dbmmanage
      Create and update user authentication files in DBM format diff --git a/docs/manual/programs/index.xml b/docs/manual/programs/index.xml index c964442673..a80c673369 100644 --- a/docs/manual/programs/index.xml +++ b/docs/manual/programs/index.xml @@ -47,6 +47,10 @@
      APache eXtenSion tool
      +
      configure
      + +
      Configure the source tree
      +
      dbmmanage
      Create and update user authentication files in DBM format diff --git a/docs/manual/sitemap.html.en b/docs/manual/sitemap.html.en index 6cd52d1f22..84a8fc9114 100644 --- a/docs/manual/sitemap.html.en +++ b/docs/manual/sitemap.html.en @@ -126,6 +126,7 @@ Server on HPUX
    • Manual Page: ab
    • Manual Page: apachectl
    • Manual Page: apxs
      • +
    • Manual Page: configure
    • Manual Page: dbmmanage
    • Manual Page: htdigest
    • Manual Page: htpasswd
      • diff --git a/docs/manual/sitemap.xml b/docs/manual/sitemap.xml index 8ac5aee95a..56182cb8f2 100644 --- a/docs/manual/sitemap.xml +++ b/docs/manual/sitemap.xml @@ -118,6 +118,7 @@ Server on HPUX Manual Page: ab Manual Page: apachectl Manual Page: apxs +Manual Page: configure Manual Page: dbmmanage Manual Page: htdigest Manual Page: htpasswd