From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2012-November/019970.html | 87 ++++++++++++++++++++++++++++ 1 file changed, 87 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-November/019970.html (limited to 'zarb-ml/mageia-dev/2012-November/019970.html') diff --git a/zarb-ml/mageia-dev/2012-November/019970.html b/zarb-ml/mageia-dev/2012-November/019970.html new file mode 100644 index 000000000..ca5833be3 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-November/019970.html @@ -0,0 +1,87 @@ + + + + [Mageia-dev] php threadsafe + + + + + + + + + +

[Mageia-dev] php threadsafe

+ AL13N + alien at rmail.be +
+ Tue Nov 13 20:10:34 CET 2012 +

+
+ +
Op dinsdag 13 november 2012 12:17:54 schreef Funda Wang:
+> 2012/11/13 Thomas Spuhler <thomas at btspuhler.com>
+> 
+> > Since this isn't a bug, I am brining it up here:
+> > The 389-ds wants apache to run with the mpm_worker_module.
+> > Apache-2.4 provides now this module as stabel
+> > 
+> > When I do this (using mpm-worker I get this error:
+> > Apache is running a threaded MPM, but your PHP Module is not compiled to
+> > be threadsafe.  You need to
+> > recompile PHP
+> > I am not quite sure how to proceed. What would be the disadvantage of
+> > compiling PHP threadsafe?
+> 
+> It is not turned on by default :(
+
+PHP? or mpm-worker? or a module that you require?
+
+if you compile threadsafe, does this mean it has a restriction on modules to 
+be threadsafe too, and maybe alot of those aren't?
+
+ + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1