On 3.02.2011 12:40, Hannes Landeholm wrote:
Can someone please explain why the child proceeds to take down the
entire server by exiting with a fatal error if it can't grab the
accept mutex and the child generation is the same as the running
generation? Whoever wrote this must have been stoned.
Hello!
Peruser is somewhat based on the prefork MPM (which is the basically
most simple MPM ever). A lot of code you see in peruser.c is in fact
from prefork. If you look at the original prefork code (line 196 at
http://svn.apache.org/viewvc/httpd/httpd/trunk/server/mpm/prefork/prefork.c?revision=1057045&view=markup
<http://svn.apache.org/viewvc/httpd/httpd/trunk/server/mpm/prefork/prefork.c?revision=1057045&view=markup>),
you can see it behaves the same way.
I think the actual problem is that it should NEVER fail to accept the
mutex. I think we had the same issue sometime and setting "AcceptMutex
flock" in the configuration file fixed the problem.
--
Taavi Sannik
DataCode OY
_______________________________________________
Peruser mailing list
[email protected]
http://www.telana.com/mailman/listinfo/peruser
