On Thu, 23 Aug 2001, Justin Erenkrantz wrote:
> If you created the locks as INTRAPROCESS before fork()ing new children,
> would each children's copy of the lock be isolated? Maybe. If so,
> then the post_config hook works, but I think child_init makes a bit
> more sense. But, that's me. -- justin
there must be other intraprocess locks created at startup time, i'd be
surprised if there's an issue. one problem with using child init is that
not all mpms support it, notice theres a few missing:
% find . -name "*.c" | xargs grep ap_run_child_init
./server/mpm/perchild/perchild.c: ap_run_child_init(pchild, ap_server_conf);
./server/mpm/prefork/prefork.c: ap_run_child_init(pchild, ap_server_conf);
./server/mpm/spmt_os2/spmt_os2.c: ap_run_child_init(pchild, ap_server_conf);
./server/mpm/threaded/threaded.c: ap_run_child_init(pchild, ap_server_conf);
./server/mpm/worker/worker.c: ap_run_child_init(pchild, ap_server_conf);
