manoj 99/04/22 00:02:52
Modified: . STATUS
Log:
saladfork.com is taken. Oh well.
Revision Changes Path
1.21 +14 -2 apache-apr/STATUS
Index: STATUS
===================================================================
RCS file: /home/cvs/apache-apr/STATUS,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -u -r1.20 -r1.21
--- STATUS 1999/04/19 04:49:15 1.20
+++ STATUS 1999/04/22 07:02:52 1.21
@@ -1,5 +1,5 @@
Apache Portable Runtime STATUS:
-Last modified at [$Date: 1999/04/19 04:49:15 $]
+Last modified at [$Date: 1999/04/22 07:02:52 $]
Release:
@@ -55,7 +55,19 @@
the server tries to kill off some children. The problem is that the
children selected may have threads blocked on the accept lock, so
they will never exit. This wasn't a problem with 1.3, because each
- process got kicked out of the lock with a signal.
+ process got kicked out of the lock with a signal. This could be solved
+ (Thanks, Dean) with a server-wide pipe that replaces the SIGWINCH signal.
+ This would wake up every thread when a single child death signal is sent
+ over the pipe.
+
+ Related to the above: On Red Hat 5.2, when we SIGTERM the server and
+ the server is in this state, the children waiting on fcntl will not
+ die, even though nobody else is holding the lock, verified with lsof.
+ The children eventually will be SIGKILLed by the parent. This only
+ happens in USE_MULTI_ACCEPT mode, and the problem goes away when
+ USE_INTRAPROCESS_SERIALIZED_ACCEPT is undefined. Dean has a couple of
+ suggestions for tracing down this problem in
+ <[EMAIL PROTECTED]>
Open issues:
