httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Stoddard" <>
Subject Re: need ap_initialize() before create_process()->...->lock_inter()->semop()
Date Wed, 23 Feb 2000 17:45:37 GMT

> IMHO, the ap_initialize() problem is the dependencies between various
> initialization procedures. At a glance, ap_initialize is not only
> suppose to do the lock related setup, but also some other in other
> platforms, which might need to be called after some initializations like
> create_process, etc. (or in the future, just guess, may need ap_alloc_init
> first somehow)
> I would suggest:
> 1. Clarify what kind of initialization will ap_initialize() do
ap_initialize() is used to initialize APR. Anything APR needs initialized
(like the locks) is done here.

> 2. Make each component as self-initialized as possible.
APR is very self contained.  The problem was that Apache started using APR
before APR was initialized. Jeff's patch should fix that.


View raw message