jkt 08/03/23 11:26:47 Modified: apache-troubleshooting.xml apache-upgrading.xml Log: Files were moved to /proj/en/apache, now for real and with an extra version bump :)
Revision Changes Path 1.8 xml/htdocs/doc/en/apache-troubleshooting.xml file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/apache-troubleshooting.xml?rev=1.8&view=markup plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/apache-troubleshooting.xml?rev=1.8&content-type=text/plain diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/apache-troubleshooting.xml?r1=1.7&r2=1.8 Index: apache-troubleshooting.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/apache-troubleshooting.xml,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- apache-troubleshooting.xml 23 Mar 2008 11:19:46 -0000 1.7 +++ apache-troubleshooting.xml 23 Mar 2008 11:26:47 -0000 1.8 @@ -1,5 +1,5 @@ <?xml version='1.0' encoding="UTF-8"?> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/apache-troubleshooting.xml,v 1.7 2008/03/23 11:19:46 jkt Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/apache-troubleshooting.xml,v 1.8 2008/03/23 11:26:47 jkt Exp $ --> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> <guide link="/doc/en/apache-troubleshooting.xml" lang="en" disclaimer="obsolete" redirect="/proj/en/apache/doc/troubleshooting.xml"> @@ -27,423 +27,17 @@ <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> <license/> -<version>1.8</version> -<date>2007-11-29</date> +<version>2</version> +<date>2008-03-23</date> <chapter> -<title>Checking the Logs</title> +<title>Moved</title> <section> <body> <p> -If there is something wrong with your Apache, but you have no idea how to -figure out what's wrong, your first clues will be in the log files. -</p> - -<p> -There are a few log files around. All of them are located inside -<path>/var/log/apache2/</path>. Not all of the following log files will be -on your system: this depends on what modules you have enabled. -</p> - -</body> -</section> - -<section> -<title>access_log and ssl_access_log</title> -<body> - -<pre caption="access_log"> -67.185.0.236 - - [18/Jun/2005:12:05:50 -0700] "GET / HTTP/1.0" 200 721 -10.0.1.80 - - [18/Jun/2005:12:11:07 -0700] "GET /~jaspenelle/__journal1.jpg HTTP/1.1" 200 19079 -66.239.233.163 - - [18/Jun/2005:12:15:06 -0700] "GET /~jaspenelle/avy14.gif HTTP/1.0" 200 1661 -67.185.60.155 - - [18/Jun/2005:12:18:48 -0700] "GET / HTTP/1.0" 200 721 -67.185.0.236 - - [18/Jun/2005:12:25:39 -0700] "GET / HTTP/1.0" 200 721 -10.0.1.80 - - [18/Jun/2005:12:28:04 -0700] "GET /~jaspenelle/avy14.gif HTTP/1.1" 200 1661 -10.0.1.80 - - [18/Jun/2005:12:28:46 -0700] "GET /~jaspenelle/avy7.png HTTP/1.1" 200 13066 -</pre> - -<p> -This file is simply a listing of every file requested from your server. Unless -you have changed the default configuration, it will be in Common Log Format: -</p> - -<pre caption="Common Log Format syntax"> -remotehost rfc931 authuser [date] "request" status bytes -</pre> - -<table> -<tr> - <ti>remotehost</ti> - <ti>Remote host name or IP address</ti> -</tr> -<tr> - <ti>rfc931</ti> - <ti>The remote log name of the user.</ti> -</tr> -<tr> - <ti>authuser</ti> - <ti>The user name as which the user has authenticated himself.</ti> -</tr> -<tr> - <ti>[date]</ti> - <ti>Date and time of the request.</ti> -</tr> -<tr> - <ti>"request"</ti> - <ti>The request line exactly as it came from the client.</ti> -</tr> -<tr> - <ti>status</ti> - <ti>The HTTP status code returned to the client.</ti> -</tr> -<tr> - <ti>bytes</ti> - <ti>The content-length of the document transferred.</ti> -</tr> -</table> - -</body> -</section> -<section> -<title>error_log and ssl_error_log</title> -<body> - -<pre caption="error_log"> -[Mon Feb 07 23:33:18 2005] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec2) -[Mon Feb 07 23:33:18 2005] [notice] Digest: generating secret for digest authentication ... -[Mon Feb 07 23:33:18 2005] [notice] Digest: done -[Mon Feb 07 23:33:18 2005] [notice] Apache/2.0.52 (Gentoo/Linux) PHP/4.3.10 configured -- resuming normal operations -[Sat Jun 18 13:01:54 2005] [error] [client 10.0.1.80] File does not exist: /var/www/localhost/htdocs/favicon.ico -[Sat Jun 18 13:02:14 2005] [error] [client 10.0.1.80] File does not exist: /var/www/localhost/htdocs/favicon.ico -[Sat Jun 18 13:02:18 2005] [error] [client 10.0.1.80] File does not exist: /var/www/localhost/htdocs/favicon.ico -[Sat Jun 18 13:02:21 2005] [error] [client 10.0.1.80] File does not exist: /var/www/localhost/htdocs/favicon.ico -[Sat Jun 18 13:02:24 2005] [error] [client 10.0.1.80] File does not exist: /var/www/localhost/htdocs/favicon.ico -</pre> - -<p> -As you can see, this file can contain a lot of stuff, depending on the -<c>ErrorLevel</c> directive in your <path>httpd.conf</path> file. It tells you -if apache started up correctly, what errors it has run into, ... In general it -will tell you what went wrong. If something isn't working right, this should -be the first file you check for more information. -</p> - -</body> -</section> -<section> -<title>suexec_log</title> -<body> - -<pre caption="suexec_log"> -[2005-02-11 22:33:19]: uid: (1000/vericgar) gid: (1000/1000) cmd: test.cgi -[2005-03-11 19:20:13]: uid: (1000/vericgar) gid: (1000/1000) cmd: test.cgi -[2005-03-11 19:34:47]: uid: (1000/vericgar) gid: (1000/1000) cmd: test.cgi -</pre> - -<p> -This file contains a log entry for every time a script is ran using CGI and -suexec. If you can't get a script to work with suexec, this log is the one -to check as it will generally have a line listing why it wouldn't run a script. -</p> - -</body> -</section> -</chapter> - -<chapter> -<title>I installed a module, but it's not working!!!</title> -<section> -<body> - -<p> -Just installing a module is not enough - you have to explicitly turn it on. We -do this so that it's easy to turn on and off individual modules, which makes -it easy to find which module is causing problems and let's you test -modules and disable them easily. -</p> - -<p> -When you install a module, it should display a message similar to this: -</p> - -<pre caption="Post-installation message from emerge"> - * - * To enable mod_layout, you need to edit your /etc/conf.d/apache2 file and - * add '-D LAYOUT' to APACHE2_OPTS. - * - * - * Configuration file installed as - * /etc/apache2/modules.d/15_mod_layout.conf - * You may want to edit it before turning the module on in /etc/conf.d/apache2 - * -</pre> - -<p> -This is pretty straightforward. It tells you exactly what you need to do to -enable this module. -</p> - -<p> -If you missed this message, there is another way to find out what you need to -add to <c>APACHE2_OPTS</c> in <path>/etc/conf.d/apache2</path>: simply -check the configuration file the module installed. The module's -configuration file should be added to <path>/etc/apache2/modules.d/</path>. -Look for it there and find a line that has <c>IfDefine</c>: -</p> - -<pre caption="An excerpt from 15_mod_layout.conf"> -<IfDefine LAYOUT> - <IfModule !mod_layout.c> - LoadModule layout_module modules/mod_layout.so - </IfModule> -</IfDefine> -</pre> - -<p> -The <c>IfDefine</c> block is ran when you add <c>-D LAYOUT</c> to -<path>/etc/conf.d/apache2</path>. The <c>LAYOUT</c> is just an example. -</p> - -<p> -There are several options you can add to <c>APACHE2_OPTS</c> that are specified -in the default configuration and well explained in -<path>/etc/conf.d/apache2</path>. -</p> - -<p> -Documentation for all of the built-in modules can be found in the <uri -link="http://httpd.apache.org/docs/2.0/";>Apache 2.0 documentation</uri>. -</p> - -</body> -</section> -</chapter> - -<chapter> -<title>Apache is returning zero-length pages or segfaulting</title> -<section> -<body> - -<p> -This happens mostly after an upgrade because binary compatibility -broke in APR (which may happen for a number for reasons). To fix this, you need -to rebuild the Apache tool stack: -</p> - -<pre caption="Rebuilding the Apache tool stack"> -<comment>(make sure you do these in order, it's very important!)</comment> - -<comment>(first, we have to remove the currently installed apache)</comment> -# <i>emerge -aCv '=www-servers/apache-2*'</i> - -<comment>(then we rebuild the tool stack)</comment> -# <i>emerge -av '=dev-libs/apr-0*' '=dev-libs/apr-util-0*'</i> - -<comment>(then we reinstall apache)</comment> -# <i>emerge -av '=www-servers/apache-2*'</i> - -<comment>(determine any packages that depend on apache)</comment> -$ <i>equery depends www-servers/apache</i> -[ Searching for packages depending on www-servers/apache... ] -dev-php/phpsysinfo-2.3-r2 -dev-php/phpsysinfo-2.1-r2 -dev-lang/php-5.2.4_p20070914-r2 -net-www/mod_layout-4.0.1a-r1 -www-servers/gorg-0.5 - -<comment>(then rebuild any modules you have installed)</comment> -# <i>emerge -av '=dev-lang/php-5.2.4_p20070914-r2' '=net-www/mod_layout-4.0.1.a-r1'</i> -</pre> - -</body> -</section> -<section> -<title>Determining a buggy add-on module</title> -<body> - -<p> -If you are still having problems after following the instructions above, the -culprit is most likely one of your installed add-on modules. -</p> - -<p> -Start off by disabling all add-on modules and restarting Apache. -</p> - -<pre caption="Disabling add-on modules"> -<comment>(edit /etc/conf.d/apache2)</comment> - -<comment>(before the change)</comment> -APACHE2_OPTS="-D PHP5 -D USERDIR -D SSL" - -<comment>(after the change)</comment> -APACHE2_OPTS="" -</pre> - -<pre caption="Restarting Apache"> -# <i>/etc/init.d/apache2 stop</i> -<comment>(make sure apache is completely stopped)</comment> -# <i>ps -A</i> -# <i>/etc/init.d/apache2 start</i> -</pre> - -<note> -You may have to make minor changes to some places of your configuration if you -have added <c>Directive</c>s that these modules provide in places that don't -test for the module being loaded. It's recommended that <c>Directive</c>s -like these be placed in test containers. See any of the .conf files in -<path>/etc/apache2/modules.d</path> examples. -</note> - -<p> -If Apache quits segfaulting and giving blank pages, then you know for sure it -was one of the add-on modules. To figure out which add-on modules, we add them -back, one at a time, completely restarting apache every time. -</p> - -<p> -When Apache stops working after adding a module back, you know that module is -the one that is causing problems. Sometimes, simply rebuilding the module -will fix the problem. -</p> - -<p> -If after rebuilding the module and restarting apache, you are still having -problems with Apache segfaulting or returning blank pages, you should <uri -link="http://bugs.gentoo.org";>file a bug</uri> listing the specific version -and revision of the module and mention that it is segfaulting. Be sure to -search for already open bugs first! -</p> - -</body> -</section> -</chapter> - -<chapter> -<title>Webserver doesn't interpret PHP or CGI scripts and returns their code -instead</title> -<section> -<body> - -<p> -Apache sometimes appears to return the PHP or CGI code instead of running those -scripts and returning the script output. If this happens even though the module -is enabled in <path>/etc/conf.d/apache2</path> it's very likely to be a cache -issue. Clearing the webbrowser cache fixes this browser side issue. -</p> - -<p> -Sometimes this problem can also be seen only when accessing the webserver using -it's DNS name but not when accessing the webserver using its IP address. This is -a strong indication that it's a cache issue. -</p> - -<p> -This problem can be fixed by clearing the webbrowser cache and any other -webproxies like squid or wwwoffle. -</p> - -</body> -</section> -</chapter> - -<chapter> -<title>configure: error: changes in the environment can compromise the build</title> -<section> -<body> - -<p> -If you get this error, then you probably have unneeded spaces in your -<c>CFLAGS</c> in <path>/etc/make.conf</path>. The fix is simple, remove the -extra spaces: -</p> - -<pre caption="Example of changes to /etc/make.conf"> -<comment>(before the change)</comment> -CFLAGS="-O2 -mcpu=pentium3 -march=pentium3 -pipe" - -<comment>(after the change - notice the removal of the space)</comment> -CFLAGS="-O2 -mcpu=pentium3 -march=pentium3 -pipe" -</pre> - -</body> -</section> -</chapter> - -<chapter> -<title>Address already in use: make_sock: could not bind to address 0.0.0.0:443</title> -<section> -<body> - -<p> -This error occurs during start-up and is caused by having multiple -<c>Listen</c> directives in your configuration that are incompatible. To solve -this problem, you should grep your configuration for <c>Listen</c> and fix each -occurrence. -</p> - -<pre caption="Finding all Listen directives"> -<comment>(Make sure you are in the configuration directory)</comment> -# <i>cd /etc/apache2/</i> - -<comment>(List all listen directives)</comment> -# <i>grep Listen httpd.conf vhosts.d/*.conf modules.d/*.conf</i> -</pre> - -<p> -What you are looking for conflicts with what Apache is trying to bind to. For -example, if there is a <c>Listen 80</c> in <path>httpd.conf</path> and there -is a <c>Listen 10.0.0.15:80</c> in another file, then Apache will not be able -to start. This is because Apache first binds to port 80 on all IP addresses -for the machine and then tries to bind to port 80 on IP address 10.0.0.15 -and fails because port 80 is already in use. -</p> - -<p> -The recommended configuration is that you have a single <c>Listen 80</c> -(this is in the default <path>httpd.conf</path>) so that you bind to all -addresses by default for the standard HTTP port and then for every SSL -<c>VirtualHost</c> you run you create a separate absolute <c>Listen</c> -directive (such as <c>Listen 10.0.0.15:443</c>). -</p> - -</body> -</section> -</chapter> - -<chapter> -<title>After upgrade to apache-2.0.54-r13 the default vhosts (SSL and non-SSL) don't work any more</title> -<section> -<body> - -<p> -With the upgrade to apache-2.0.54-r13, two new directives were added to it -to fix <uri link="http://bugs.gentoo.org/show_bug.cgi?id=100624";>bug -100624</uri>. -</p> - -<p> -The new directives are <c>-D DEFAULT_VHOST</c> to activate the default -virtual host and <c>-D SSL_DEFAULT_VHOST</c> to activate the default SSL -virtual host. Both need to be added to the <c>APACHE2_OPTS</c> variable in -<path>/etc/conf.d/apache2</path> if you want Apache to behave like before. -</p> - -</body> -</section> -</chapter> - -<chapter id="getting-help"> -<title>Getting Help</title> -<section> -<body> - -<p> -If none of the above was of any use to you, or if you have other questions, -feel free to stop by our IRC channel, <path>#gentoo-apache</path> on -<path>irc.freenode.net</path>. Or you may also file a bug on <uri -link="http://bugs.gentoo.org";>Gentoo's Bugzilla</uri>. +This document has been moved to a <uri +link="/proj/en/apache/doc/troubleshooting.xml">new location</uri>. </p> </body> 1.14 xml/htdocs/doc/en/apache-upgrading.xml file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/apache-upgrading.xml?rev=1.14&view=markup plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/apache-upgrading.xml?rev=1.14&content-type=text/plain diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/apache-upgrading.xml?r1=1.13&r2=1.14 Index: apache-upgrading.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/apache-upgrading.xml,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- apache-upgrading.xml 23 Mar 2008 11:19:46 -0000 1.13 +++ apache-upgrading.xml 23 Mar 2008 11:26:47 -0000 1.14 @@ -1,6 +1,6 @@ <?xml version='1.0' encoding="UTF-8"?> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/apache-upgrading.xml,v 1.13 2008/03/23 11:19:46 jkt Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/apache-upgrading.xml,v 1.14 2008/03/23 11:26:47 jkt Exp $ --> <guide link="/doc/en/apache-upgrading.xml" lang="en" disclaimer="obsolete" redirect="/proj/en/apache/doc/upgrading.xml"> <title>Upgrading Apache</title> @@ -24,762 +24,21 @@ <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> <license/> -<version>2.8</version> -<date>2007-12-11</date> +<version>3</version> +<date>2008-03-23</date> -<chapter id="upgrade-2.2.6-r4"> -<title>Upgrading from <2.2.6-r4</title> +<chapter> +<title>Moved</title> <section> <body> <p> -The Apache ebuilds have used <path>/etc/apache2/apache2-builtin-mods</path> for -a very long time to select the built-in modules during compile time. However, -this behavior has several disadvantages: -</p> - -<ul> - <li> - Selecting built-in modules during the initial merge is not possible - </li> - <li> - Portage does not know which modules have been installed. This is especially - annoying for binary packages. - </li> - <li> - Portage will try to overwrite <path>apache2-builtin-mods</path> on every - upgrade - </li> -</ul> - -<p> -To rectify this situation <path>/etc/apache2/apache2-builtin-mods</path> has -been deprecated and migrated to the new <c>APACHE2_MODULES</c> <c>USE_EXPAND</c> -variable. To convert your custom module selection to the new format use the -following command: -</p> - -<pre caption="Convert apache2-builtin-mods to APACHE2_MODULES"> -$ <i>echo APACHE2_MODULES=\"$(sed '/^mod_/s/mod_\(.*\)\s\+\(shared\|static\)/\1/;t n;d;:n' /etc/apache2/apache2-builtin-mods)\" >> /etc/make.conf</i> -# <i>rm /etc/apache2/apache2-builtin-mods</i> - -<comment>(You can now safely upgrade apache:)</comment> -# <i>emerge -uva '>=www-servers/apache-2.2.6-r4'</i> -</pre> - -<p> -Additionally to the new <c>APACHE2_MODULES</c> the local USE flags have been -cleaned up: -</p> - -<ul> - <li> - All MPM USE flags have been moved to the <c>APACHE2_MPMS</c> - <c>USE_EXPAND</c> variable - </li> - <li> - <c>no-suexec</c> is now <c>suexec</c> - </li> - <li> - <c>static-modules</c> is now <c>static</c> - </li> -</ul> - -<p> -For a detailed description of old and corresponding new USE flags see <uri -link="#use-2.2.6-r4">below</uri>. -</p> - -</body> -</section> -</chapter> - -<chapter id="upgrade-2.0.52-r3"> -<title>Upgrading from <2.0.52-r3</title> -<section> -<title>Introduction</title> -<body> - -<p> -The state of Apache and its modules in Gentoo was becoming dismal. There were a -number of problems that caused support problems and made maintaining everything -the Apache herd is responsible for difficult: -</p> - -<ul> - <li> - The configuration that came with Gentoo was dramatically different from - the upstream configuration that most users expect - </li> - <li> - Many modules used similar code, but all did things their own way - </li> - <li> - Most modules weren't maintained very well - mostly because of the large - number of modules available - </li> - <li>Modules didn't have a configuration standard</li> - <li> - Some modules could support both versions of Apache, but the ebuilds - didn't handle that - </li> - <li> - Choices available in Apache were not available for Gentoo users (for - example MPMs) - </li> - <li>Bugs for Apache were stacking up</li> -</ul> - -<p> -This document details how to upgrade without breaking your system. If you are -a developer or would like to know what we changed, or how ebuilds need to be -modified to take advantage of our eclass, then check the <uri -link="/proj/en/apache/apache-developer.xml">Apache Developer Reference</uri>. -</p> - -</body> -</section> -<section> -<title>Upgrading</title> -<body> - -<p> -There have been many changes to how Apache works within Gentoo. Every package -that is directly related to Apache needs to be updated and some things that -worked previously will no longer work. -</p> - -<p> -First you need to figure out what packages you need to upgrade. You can do this -using the <c>equery</c> tool, which is part of the -<c>app-portage/gentoolkit</c> package. -</p> - -<pre caption="Finding packages to update"> -$ <i>equery depends www-servers/apache</i> -[ Searching for packages depending on www-servers/apache... ] -dev-db/phpmyadmin-2.5.6 -dev-php/mod_php-4.3.10 -dev-php/phpsysinfo-2.1-r2 -net-www/mod_bandwidth-2.0.5 -net-www/mod_layout-4.0.1a -net-www/mod_mp3-0.40 -net-www/mod_random-2.0 -net-www/mod_throttle-3.1.2-r1 -www-apache/mod_ldap_userdir-1.1.4 -www-apache/mod_loopback-1.04 -www-apache/mod_watch-3.18 -www-apps/viewcvs-0.9.2_p20030430 -</pre> - -<impo> -The packages you have installed may be vastly different; make sure you run this -command for yourself. -</impo> - -<warn> -There are some modules and packages that depend on Apache that have not yet -been updated. Please <uri link="http://bugs.gentoo.org";>search bugzilla</uri> -for any critical packages that you use with Apache. -</warn> - -<p> -Many webapps aren't affected in any way as most use the <c>webapp</c> eclass -which takes care of installing them correctly. You may want to check to see if -there is a new revision. -</p> - -<p> -As we have added some new USE flags, you may want to review them and add -appropriate lines to <path>/etc/portage/package.use</path>. See <uri -link="#use-2.2.6-r4">Apache supported USE flags</uri> for more details. -</p> - -<pre caption="Checking USE flag settings and rebuild"> -<comment>(Check the USE flags and needed updates)</comment> -# <i>emerge --pretend --verbose --update --newuse --deep apache subversion \ -mod_php mod_bandwidth mod_layout mod_ldap_userdir mod_loopback mod_mp3 \ -mod_random mod_throttle mod_watch</i> - -<comment>(Update the packages)</comment> -# <i>emerge --verbose --update --newuse --deep apache subversion mod_php \ -mod_bandwidth mod_layout mod_ldap_userdir mod_loopback mod_mp3 mod_random \ -mod_throttle mod_watch</i> - -<comment>(It may be easier to just update world instead of the above)</comment> -# <i>emerge --ask --verbose --update --newuse --deep world</i> -</pre> - -<p> -Now you need to reconfigure Apache and its modules. Start by using -<c>etc-update</c> or <c>dispatch-conf</c> to update the <path>/etc/init.d</path> -and <path>/etc/conf.d</path> files. You will notice that your apache -configuration files won't show up in the updates - this is because all the -configuration files have moved. -</p> - -<p> -If you have made changes to the previous default <path>apache.conf</path> and -<path>commonapache.conf</path> you will need to migrate your changes to -<path>/etc/apache{|2}/httpd.conf</path>. Also configuration locations for -modules and virtual hosts have changed -- they are now located in -<path>/etc/apache2/modules.d</path> and <path>/etc/apache2/vhosts.d</path> -respectively. -</p> - -<p> -When you have finished migrating your changes to the new configuration file, -you will need to delete the old configuration files (or move them to a safe -place). The new <path>/etc/init.d/apache{|2}</path> checks for these files and -doesn't let you start apache unless you have removed them, indicating that you -have reconfigured apache using the new paths. -</p> - -<note> -Many modules that used to be enabled by default are now disabled. If they are -apache built-in modules, then uncomment the appropriate line in httpd.conf. -If they are external modules, check the module's .conf for <c>IfDefine</c> and -add the name to <path>/etc/conf.d/apache{|2}</path> to enable it. -</note> - -<p> -Now you may restart apache. -</p> - -<pre caption="Restarting apache"> -# <i>/etc/init.d/apache stop</i> -# <i>/etc/init.d/apache start</i> -</pre> - -<p> -If you run into any problems check the <uri -link="/doc/en/apache-troubleshooting.xml">Apache Troubleshooting Guide</uri> -and if that doesn't solve the issue, please report it on <uri -link="http://bugs.gentoo.org";>Gentoo Bugzilla</uri>. Be sure to include the -modules you have enabled and (if you are using Apache 2) what MPM USE flag you -compiled with (if any). You may also join <path>#gentoo-apache</path> on -<path>irc.freenode.net</path> for support. +This document has been moved to a <uri +link="/proj/en/apache/doc/upgrading.xml">new location</uri>. </p> </body> </section> </chapter> -<chapter id="use-pre-2.2.6-r4"> -<title>Supported USE flags in <2.2.6-r4</title> -<section> -<body> - - -<p> -There are USE flags that are local to apache and its modules. Apache -supports several other more generic USE flags such as <c>ssl</c>, but the -effect they have on apache doesn't differ much from the effect is has elsewhere, -so it's not included in this list. Run a <c>emerge --verbose --pretend -apache</c> to see the full listing of supported USE flags. -</p> - -<table> -<tr> - <th>USE flag</th> - <th>Description</th> -</tr> -<tr> - <ti>apache2</ti> - <ti> - Should always be set if using the Apache-2.0 line, should not be set if - using the Apache-1.3 line. The eclass uses this to determine what version of - apache to depend on. - </ti> -</tr> -<tr> - <ti>debug</ti> - <ti> - Enables a hook that allows external modules to plug in and do something - after a child crashed. There are already two modules, - <c>mod_whatkilledus</c> and <c>mod_backtrace</c> that make use of this - hook. - </ti> -</tr> -<tr> - <ti>doc</ti> - <ti> - Install the Apache manual and configuration. - </ti> -</tr> -<tr> - <ti>ldap</ti> - <ti> - Install <c>mod_ldap</c> and <c>mod_auth_ldap</c>/<c>mod_authnz_ldap</c>. - </ti> -</tr> -<tr> - <ti>ssl</ti> - <ti> - Installs <c>mod_ssl</c>. - </ti> -</tr> -<tr> - <ti>mpm-itk</ti> - <ti>Builds the <uri link="http://mpm-itk.sesse.net/";>itk</uri> MPM</ti> -</tr> -<tr> - <ti>mpm-leader</ti> - <ti> - Builds the <uri - link="http://httpd.apache.org/docs/2.0/mod/leader.html";>leader</uri> MPM - </ti> -</tr> -<tr> - <ti>mpm-peruser</ti> - <ti> - Builds the <uri link="http://www.telana.com/peruser.php";>peruser</uri> MPM - </ti> -</tr> -<tr> - <ti>mpm-prefork</ti> - <ti> - Builds the <uri - link="http://httpd.apache.org/docs/2.0/mod/prefork.html";>prefork</uri> - MPM</ti> -</tr> -<tr> - <ti>mpm-threadpool</ti> - <ti> - Builds the <uri - link="http://httpd.apache.org/docs/2.0/mod/threadpool.html";>threadpool</uri> - MPM - </ti> -</tr> -<tr> - <ti>mpm-worker</ti> - <ti> - Builds the <uri - link="http://httpd.apache.org/docs/2.0/mod/worker.html";>worker</uri> MPM - </ti> -</tr> -<tr> - <ti>static-modules</ti> - <ti> - Statically links the modules into the apache binary, so that a - LoadModule isn't required for loading the base modules into - Apache. - </ti> -</tr> -</table> - -<note> -While there are many <c>mpm-*</c> USE flags, they are mutually exclusive. You -should enable one and only one of the <c>mpm-*</c> USE flags. (If you do not -enable one, <c>mpm-prefork</c> or <c>mpm-worker</c> will be used, depending on -if the threads USE flag is set.) -</note> - -</body> -</section> -</chapter> - -<chapter id="use-2.2.6-r4"> -<title>Supported USE flags in 2.2.6-r4 and above</title> -<section> -<body> - -<p> -With the advent of <c>APACHE2_MODULES</c> a general cleanup of USE flags was -necessary. The following table lists supported USE flags for -<c>apache-2.2.6-r4</c> and above as well as their equivalent in previous -versions. -</p> - -<table> -<tr> - <th>USE flag</th> - <th>Old USE flag</th> - <th>Description</th> -</tr> -<tr> - <ti>debug</ti> - <ti>debug</ti> - <ti> - Enables a hook that allows external modules to plug in and do something - after a child crashed. There are already two modules, - <c>mod_whatkilledus</c> and <c>mod_backtrace</c>, that make use of this - hook. - </ti> -</tr> -<tr> - <ti>doc</ti> - <ti>doc</ti> - <ti>Install the Apache manual and configuration.</ti> -</tr> -<tr> - <ti>ldap</ti> - <ti>ldap</ti> - <ti>Install <c>mod_ldap</c> and <c>mod_authnz_ldap</c></ti> -</tr> -<tr> - <ti>ssl</ti> - <ti>ssl</ti> - <ti>Installs <c>mod_ssl</c></ti> -</tr> -<tr> - <ti>static</ti> - <ti>static-modules</ti> - <ti> - Statically links the modules into the apache binary, so that a LoadModule - isn't required for loading the base modules into Apache - </ti> -</tr> -<tr> - <ti>suexec</ti> - <ti>no-suexec</ti> - <ti>Install <c>mod_suexec</c> and the <c>suexec</c> helper binary</ti> -</tr> -<tr> - <ti>threads</ti> - <ti>threads</ti> - <ti>Selects the default MPM if none is set in APACHE2_MPMS</ti> -</tr> -</table> - -<p> -The following table lists supported <c>APACHE2_MPMS</c> as of -<c>apache-2.2.6-r4</c> and their corresponding previous local USE flag. -</p> - -<table> -<tr> - <th>Flag</th> - <th>Old USE flag</th> - <th>Description</th> -</tr> -<tr> - <ti>event</ti> - <ti>mpm-event</ti> - <ti>An experimental variant of the standard worker MPM</ti> -</tr> -<tr> - <ti>itk</ti> - <ti>mpm-itk</ti> - <ti>Allows to run each virtual host under a separate uid and gid</ti> -</tr> -<tr> - <ti>peruser</ti> - <ti>mpm-peruser</ti> - <ti> - Peruser is a working implementation of the perchild MPM allowing to run each - apache child process as its own user and group, each handling its own set of - virtual hosts - </ti> -</tr> -<tr> - <ti>prefork</ti> - <ti>mpm-prefork</ti> - <ti>Implements a non-threaded, pre-forking web server</ti> -</tr> -<tr> - <ti>worker</ti> - <ti>mpm-worker</ti> - <ti> - Multi-Processing Module implementing a hybrid multi-threaded multi-process - web server - </ti> -</tr> -</table> - -<p> -The following table lists supported <c>APACHE2_MODULES</c> as of -<c>apache-2.2.6-r4</c>. -</p> - -<table> -<tr> - <th>Flag</th> - <th>Description</th> -</tr> -<tr> - <ti>actions</ti> - <ti> - Provides for executing CGI scripts based on media type or request method - </ti> -</tr> -<tr> - <ti>alias</ti> - <ti> - Provides for mapping different parts of the host filesystem in the - document tree and for URL redirection - </ti> -</tr> -<tr> - <ti>asis</ti> - <ti>Sends files that contain their own HTTP headers</ti> -</tr> -<tr> - <ti>auth_basic</ti> - <ti>Basic authentication</ti> -</tr> -<tr> - <ti>auth_digest</ti> - <ti>User authentication using MD5 Digest Authentication</ti> -</tr> -<tr> - <ti>authn_alias</ti> - <ti> - Provides the ability to create extended authentication providers based on - actual providers - </ti> -</tr> -<tr> - <ti>authn_anon</ti> - <ti>Allows "anonymous" user access to authenticated areas</ti> -</tr> -<tr> - <ti>authn_dbd</ti> - <ti>User authentication using an SQL database</ti> -</tr> -<tr> - <ti>authn_dbm</ti> - <ti>User authentication using DBM files</ti> -</tr> -<tr> - <ti>authn_default</ti> - <ti>Authentication fallback module</ti> -</tr> -<tr> - <ti>authn_file</ti> - <ti>User authentication using text files</ti> -</tr> -<tr> - <ti>authz_dbm</ti> - <ti>Group authorization using DBM files</ti> -</tr> -<tr> - <ti>authz_default</ti> - <ti>Authorization fallback module</ti> -</tr> -<tr> - <ti>authz_groupfile</ti> - <ti>Group authorization using plaintext files</ti> -</tr> -<tr> - <ti>authz_host</ti> - <ti>Group authorizations based on host (name or IP address)</ti> -</tr> -<tr> - <ti>authz_owner</ti> - <ti>Authorization based on file ownership</ti> -</tr> -<tr> - <ti>authz_user</ti> - <ti>User Authorization</ti> -</tr> -<tr> - <ti>autoindex</ti> - <ti> - Generates directory indexes automatically, similar to the Unix <c>ls</c> - command - </ti> -</tr> -<tr> - <ti>cache</ti> - <ti>Content cache keyed to URIs</ti> -</tr> -<tr> - <ti>cern_meta</ti> - <ti>CERN httpd metafile semantics</ti> -</tr> -<tr> - <ti>charset_lite</ti> - <ti>Specify character set translation or recoding</ti> -</tr> -<tr> - <ti>dav</ti> - <ti>Distributed Authoring and Versioning (WebDAV) functionality</ti> -</tr> -<tr> - <ti>dav_fs</ti> - <ti>filesystem provider for mod_dav</ti> -</tr> -<tr> - <ti>dav_lock</ti> - <ti>generic locking module for mod_dav</ti> -</tr> -<tr> - <ti>dbd</ti> - <ti>Manages SQL database connections</ti> -</tr> -<tr> - <ti>deflate</ti> - <ti>Compress content before it is delivered to the client</ti> -</tr> -<tr> - <ti>dir</ti> - <ti> - Provides for "trailing slash" redirects and serving directory index files - </ti> -</tr> -<tr> - <ti>disk_cache</ti> - <ti>Content cache storage manager keyed to URIs</ti> -</tr> -<tr> - <ti>dumpio</ti> - <ti>Dumps all I/O to error log as desired</ti> -</tr> -<tr> - <ti>env</ti> - <ti>Modifies the environment which is passed to CGI scripts and SSI pages</ti> -</tr> -<tr> - <ti>expires</ti> - <ti> - Generation of Expires and Cache-Control HTTP headers according to - user-specified criteria - </ti> -</tr> -<tr> - <ti>ext_filter</ti> - <ti> - Pass the response body through an external program before delivery to the - client - </ti> -</tr> -<tr> - <ti>file_cache</ti> - <ti>Caches a static list of files in memory</ti> -</tr> -<tr> - <ti>filter</ti> - <ti>Context-sensitive smart filter configuration module</ti> -</tr> -<tr> - <ti>headers</ti> - <ti>Customization of HTTP request and response headers</ti> -</tr> -<tr> - <ti>ident</ti> - <ti>RFC 1413 ident lookups</ti> -</tr> -<tr> - <ti>imagemap</ti> - <ti>Server-side imagemap processing</ti> -</tr> -<tr> - <ti>include</ti> - <ti>Server-parsed html documents (Server Side Includes)</ti> -</tr> -<tr> - <ti>info</ti> - <ti>Provides a comprehensive overview of the server configuration</ti> -</tr> -<tr> - <ti>log_config</ti> - <ti>Logging of the requests made to the server</ti> -</tr> -<tr> - <ti>log_forensic</ti> - <ti>Forensic Logging of the requests made to the server</ti> -</tr> -<tr> - <ti>logio</ti> - <ti>Logging of input and output bytes per request</ti> -</tr> -<tr> - <ti>mem_cache</ti> - <ti>Content cache keyed to URIs</ti> -</tr> -<tr> - <ti>mime</ti> - <ti> - Associates the requested filename's extensions with the file's behavior - (handlers and filters) and content (mime-type, language, character set and - encoding) - </ti> -</tr> -<tr> - <ti>mime_magic</ti> - <ti> - Determines the MIME type of a file by looking at a few bytes of its - contents - </ti> -</tr> -<tr> - <ti>negotiation</ti> - <ti>Provides for content negotiation</ti> -</tr> -<tr> - <ti>proxy</ti> - <ti>HTTP/1.1 proxy/gateway server</ti> -</tr> -<tr> - <ti>proxy_ajp</ti> - <ti>AJP support module for mod_proxy</ti> -</tr> -<tr> - <ti>proxy_balancer</ti> - <ti>mod_proxy extension for load balancing</ti> -</tr> -<tr> - <ti>proxy_connect</ti> - <ti>mod_proxy extension for CONNECT request handling</ti> -</tr> -<tr> - <ti>proxy_ftp</ti> - <ti>FTP support module for mod_proxy</ti> -</tr> -<tr> - <ti>proxy_http</ti> - <ti>HTTP support module for mod_proxy</ti> -</tr> -<tr> - <ti>rewrite</ti> - <ti> - Provides a rule-based rewriting engine to rewrite requested URLs on the fly - </ti> -</tr> -<tr> - <ti>setenvif</ti> - <ti> - Allows the setting of environment variables based on characteristics of the - request - </ti> -</tr> -<tr> - <ti>speling</ti> - <ti> - Attempts to correct mistaken URLs that users might have entered by - ignoring capitalization and by allowing up to one misspelling - </ti> -</tr> -<tr> - <ti>status</ti> - <ti>Provides information on server activity and performance</ti> -</tr> -<tr> - <ti>unique_id</ti> - <ti> - Provides an environment variable with a unique identifier for each request - </ti> -</tr> -<tr> - <ti>userdir</ti> - <ti>User-specific directories</ti> -</tr> -<tr> - <ti>usertrack</ti> - <ti>Clickstream logging of user activity on a site</ti> -</tr> -<tr> - <ti>version</ti> - <ti>Version dependent configuration</ti> -</tr> -<tr> - <ti>vhost_alias</ti> - <ti>Provides for dynamically configured mass virtual hosting</ti> -</tr> -</table> - -</body> -</section> -</chapter> </guide> -- [email protected] mailing list
