On 2/22/2010 11:16 AM, [email protected] wrote: > Author: trawick > Date: Mon Feb 22 17:16:29 2010 > New Revision: 912666 > > URL: http://svn.apache.org/viewvc?rev=912666&view=rev > Log: > Fix startup segfault when the Mutex directive is used but no loaded > modules use httpd mutexes. > > Add an init call from core's pre-config hook to ensure init is > performed before the config is parsed.
This logic seems broken. The problem is that anonymous mutexes against a persistant data store can't be closed and reopened between server generations. This use of pre/post config persists the broken design. This layer of init really should happen against process pool, within the scope of the register hooks. No? There's no hassle for a named mutex object that corresponds to the persistent object, e.g. a named file lock against a named database.
