coar 99/08/06 10:52:39
Modified: . STATUS
Log:
Add notes about memory leaks found by David Harris. It's
unclear (to me, at least) how severe they are, but the
module counters are involved and long-running servers with regularly
scheduled restarts *could* be vulnerable..?
Revision Changes Path
1.736 +14 -5 apache-1.3/STATUS
Index: STATUS
===================================================================
RCS file: /home/cvs/apache-1.3/STATUS,v
retrieving revision 1.735
retrieving revision 1.736
diff -u -r1.735 -r1.736
--- STATUS 1999/08/05 18:42:20 1.735
+++ STATUS 1999/08/06 17:52:37 1.736
@@ -1,12 +1,15 @@
1.3 STATUS:
- Last modified at [$Date: 1999/08/05 18:42:20 $]
+ Last modified at [$Date: 1999/08/06 17:52:37 $]
Release:
- 1.3.8-dev: current. 'Quiet mode' on 6 August 1999, then internal
- testing until 12 August 1999. If no problems, roll on
+ 1.3.8-dev: current. 'Quiet mode' on 6 August 1999; should we roll
+ then, or wait for internal testing first? The
+ -testers lists get the tarball as soon as it's rolled.
+ Current plan: test internally. If no problems, roll on
12 August and submit to -testers lists, then release on
- Monday 16 August 1999. Ken is RM.
+ Monday 16 August 1999. Roy wants it to happen faster.
+ Ken is RM.
1.3.7: Not released.
1.3.6. Tagged and rolled on Mar. 22. Released and announced on 24th.
@@ -71,7 +74,13 @@
RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
- * Graham Legget has found that if he uses the 1.3.7-dev core, and
+ * David Harris' note of leakage problems in adding/removing
+ modules, plus additional findings by Dean and Jim. Discussion
+ in thread following message-ID below.
+ Message-ID: <[EMAIL PROTECTED]>
+ Status:
+
+ * Graham Leggett has found that if he uses the 1.3.7-dev core, and
the 1.3.6 proxy code (plus a small patch of his) he doesn't get
the hangs he was reporting. The situation is better as of
18 July 1999; still an occasional problem, but no longer a
