diff options
author | pcs <pcs@unknown> | 1997-07-11 13:01:19 +0000 |
---|---|---|
committer | pcs <pcs@unknown> | 1997-07-11 13:01:19 +0000 |
commit | 2c25910d87137d2b1cc549ac4bc69c3b01257c68 (patch) | |
tree | 7c5b60676d187c8e8392343afb1c0e306c7a4668 | |
parent | d76a179806499cb9831375ee7d028cbaf0dfc3a1 (diff) | |
download | httpd-2c25910d87137d2b1cc549ac4bc69c3b01257c68.tar.gz |
Bring known bugs in 1_2_X up-to-date from HEAD
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/1.3@78588 13f79535-47bb-0310-9956-ffa450edef68
-rw-r--r-- | APACHE_1_2_X/htdocs/manual/misc/known_bugs.html | 54 |
1 files changed, 43 insertions, 11 deletions
diff --git a/APACHE_1_2_X/htdocs/manual/misc/known_bugs.html b/APACHE_1_2_X/htdocs/manual/misc/known_bugs.html index 8ce19caeff..cc37690299 100644 --- a/APACHE_1_2_X/htdocs/manual/misc/known_bugs.html +++ b/APACHE_1_2_X/htdocs/manual/misc/known_bugs.html @@ -27,8 +27,41 @@ in early versions have been fixed in 1.2. <H2>Apache 1.2 Bugs</H2> -<OL><a name="listenbug"></a> - <LI>On some architectures if your configuration uses multiple +<OL> + <LI><b>Exists in 1.2.1 only.</b> + On Solaris 2.x the server will stop running after receiving a + SIGHUP. Four workarounds exist (choose one):<p> + <ul> + <li>Retrieve <a href="http://www.apache.org/dist/patches/apply_to_1.2.1/solaris_hup.patch">this patch</a>. + <code>cd</code> to your <code>apache_1.2.1</code> directory, and + type <code>patch -s -p1 < /path/to/patchfile</code>. Then rebuild + Apache.<p> + <li>Use SIGUSR1 instead of SIGHUP, see <a href="../stopping.html"> + Stopping and Restarting Apache</a> for more details.<p> + <li>Add <code>-DNO_SLACK</code> to + <code>EXTRA_CFLAGS</code> in + your <code>Configuration</code> file, re-run <code>Configure</code> + and rebuild your server. This disables the + <a href="descriptors.html">descriptor slack workaround</a><p> + <li>(Least preferable) Use Apache 1.2.0 instead of 1.2.1.<p> + </ul> + This problem will be tracked as + <a href="http://www.apache.org/bugdb.cgi/full/832">PR#832</a>.<p> + </li> + + <LI>(Exists in 1.2.0 and in 1.2.1 after either of the + <code>NO_SLACK</code> or patch provided by the previous bug are applied.) + Solaris 2.5.1 (and probably other versions of Solaris) appear to have + a race condition completely unrelated to all the others. It is possible + during a SIGHUP that the server will fail to start because it will not + be able to re-open its sockets. To our knowledge this has only shown + up during testing when we pummel the server with as many SIGHUP requests + per second as we can. This appears unrelated to the similar sounding bug + described in <a href="http://www.apache.org/bugdb.cgi/full/832">PR#832</a>. + <p> + + <LI><a name="listenbug">On some architectures</A> + if your configuration uses multiple <a href="../mod/core.html#listen">Listen</a> directives then it is possible that the server will starve one of the sockets while serving hits on another. The work-around is to add @@ -43,12 +76,11 @@ in early versions have been fixed in 1.2. <a href="http://www.apache.org/bugdb.cgi/full/467">PR#467</a>. <P></LI> - <a name="cnegbug"></a> <LI><b>Fixed in 1.2.1.</b> - Apache's <A HREF="../content-negotiation.html">Content + <a name="cnegbug">Apache's</A> <A HREF="../content-negotiation.html">Content Negotiation</A> should pick the smallest variant if there are several that are equally acceptable. A bug in 1.2 means it no - longer does this unless all the variants have character sets. + longer does this unless all the variants have character sets. This <A HREF="../../dist/contrib/patches/1.2/conneg-bug.patch">patch</A> fixes this problem. It also fixes the problem which makes Apache pick the last equally acceptable variant instead of the first. @@ -58,7 +90,7 @@ in early versions have been fixed in 1.2. <LI> The PATH_INFO part of a request URI cannot include the sequence - <CODE>%2f</CODE>. This will be tracked as + <CODE>%2f</CODE>. This will be tracked as <A HREF="http://www.apache.org/bugdb.cgi/full/543">PR#543</A>. <P></LI> @@ -80,15 +112,15 @@ in early versions have been fixed in 1.2. <LI>If compilation fails complaining about "unknown symbol __inet_ntoa()" then you have probably installed version 8 of bind. You will need to - explicitly link with the bind library by adding <CODE>-lbind</CODE> - to <CODE>EXTRA_LFLAGS</CODE> in <CODE>Configuration</CODE>. See + explicitly link with the bind library by adding <CODE>-lbind</CODE> + to <CODE>EXTRA_LDFLAGS</CODE> in <CODE>Configuration</CODE>. See <A HREF="http://www.apache.org/bugdb.cgi/full/616">PR#616</A> - and the + and the <A HREF="FAQ.html#bind8.1">Apache FAQ</A>. <P></LI> <LI>The message "<CODE>created shared memory segment #730499</CODE>" - in error_log is not an error and should be ignored. See + in error_log is not an error and should be ignored. See <a href="http://www.apache.org/bugdb.cgi/full/696">PR#696</A>. <P></LI> @@ -104,7 +136,7 @@ in early versions have been fixed in 1.2. virtual hosts. This appears similar to a file-descriptor limit but BSDI should not have this problem. This will be tracked as <A HREF="http://www.apache.org/bugdb.cgi/full/611">PR#611</A>. - See also the <A HREF="FAQ.html#fdlim">Apache FAQ</A>. + See also the <A HREF="FAQ.html#fdlim">Apache FAQ</A>. <P></LI> <LI><a href="descriptors.html"><b>Workaround available in 1.2.1.</b></a> |