[Mono-bugs] [Bug 68854][Cri] Changed - mod_mono returns 503 when using the Apache 2 "worker" MPM
Thu, 3 Feb 2005 19:45:37 -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 email@example.com.
--- shadow/68854 2005-02-03 14:32:03.000000000 -0500
+++ shadow/68854.tmp.22492 2005-02-03 19:45:37.000000000 -0500
@@ -245,6 +245,17 @@
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.
+------- Additional Comments From firstname.lastname@example.org 2005-02-03 19:45 -------
+I was thinking if we should just make the synchronization work using
+apache 2 API and forget about it for apache 1. And we should use an
+apache mutex, as creating a file might not always work (see the code
+for lockfile tool and liblockfile).
+After further testing on apache 1, I'll commit your patch using
+apache2 mutex around the process startup. It will be in svn tonight.