[Mono-bugs] [Bug 68854][Cri] Changed - mod_mono returns 503 when using the Apache 2 "worker" MPM

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Thu, 3 Feb 2005 14:32:03 -0500 (EST)

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by rlyon@novell.com.


--- shadow/68854	2005-02-03 04:32:55.000000000 -0500
+++ shadow/68854.tmp.20007	2005-02-03 14:32:03.000000000 -0500
@@ -215,6 +215,36 @@
 If you want to complete the patch for these things, tell me, otherwise
 i'll finish it tomorrow (3:34 am now) and figure out what to do with
+------- Additional Comments From rlyon@novell.com  2005-02-03 14:32 -------
+You don't need the wait() to get rid the zombies, just the second 
+fork that I should not have taken out: 
+    // new process fork 
+    if (fork() != 0) { 
+        return; 
+	} 
+    // daemonize fork 
+    if (fork() != 0) { 
+        exit(0); 
+    } 
+I don't understand your concern with the finalization code -- it 
+works the same as it always did and is only tied to the pool cleanup 
+and not the process cleanup.  Mike and I verified that it is only 
+being called once when Apache rolls. (It was being called one other 
+time between the first call and second call of post_config without 
+causing a problem, but that is not happening any because of the new 
+user data check.) 
+Do you have a suggestions on tightening the synchronization around 
+the start of mod-mono-server?  The mod-mono-server application takes 
+care of it itself by failing on the socket file, but we could bring 
+it up to make it tighter.  Mike used a file in mod_simias.  We could 
+also use a mutex and/or an atomic flag.