Oh, FreeBSD, you don't like having multiple children, do you?

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

diff --git a/STATUS b/STATUS
index 23e54ec42d1c14657279a7461998a7c3c471aab6..8652a8466e0e0f6088abb8022d256c720d1dab3a 100644 (file)
--- a/STATUS
+++ b/STATUS
@@ -1,5 +1,5 @@
 APACHE 2.0 STATUS:                                             -*-text-*-
-Last modified at [$Date: 2001/12/08 01:38:04 $]
+Last modified at [$Date: 2001/12/12 10:09:58 $]
 
 Release:
 
@@ -94,6 +94,13 @@ RELEASE SHOWSTOPPERS:
 
 RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
 
+    * FreeBSD, threads, and worker MPM.  All seems to work fine 
+      if you only have one worker process with many threads.  Add 
+      a second worker process and the accept lock seems to be
+      lost.  This might be an APR issue with how it deals with
+      the child_init hook (i.e. the fcntl lock needs to be resynced).
+      More examination and analysis is required.
+     
     * There is increasing demand from module writers for an API
       that will allow them to control the server à la apachectl.
       Reasons include sole-function servers that need to die if