From: Justin Erenkrantz <jerenkrantz@apache.org>
Date: Fri, 7 Dec 2001 18:02:47 +0000 (+0000)
Subject: Any release that goes out that doesn't have this fixed is getting vetoed
X-Git-Tag: 2.0.30~261
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=a519d09fa5ca2184e3267e3554aea029e531a46d;p=thirdparty%2Fapache%2Fhttpd.git

Any release that goes out that doesn't have this fixed is getting vetoed
by me as anything other than alpha.

I'm sick of this - it's been a pain for a long time and just hit me
hard when one of the other admins on my 2.0 site tried to send SIGHUP
and the thing died - it confused the hell out of him.  =)

Let's start tracking this down.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@92371 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/STATUS b/STATUS
index a31ddbf1cde..241fe6c5a17 100644
--- a/STATUS
+++ b/STATUS
@@ -1,5 +1,5 @@
 APACHE 2.0 STATUS:						-*-text-*-
-Last modified at [$Date: 2001/12/07 15:41:00 $]
+Last modified at [$Date: 2001/12/07 18:02:47 $]
 
 Release:
 
@@ -92,6 +92,9 @@ RELEASE SHOWSTOPPERS:
       any) to segfault on AIX and can probably cause load or other
       errors on some other platforms.
 
+    * Sending httpd a SIGHUP with worker MPM causes a segfault 
+      when we started as root and switch to a different user.
+
 RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
 
     * There is increasing demand from module writers for an API