At 02:18 PM 11/10/2003, you wrote: >Bill Stoddard wrote: >[...] >>> Any ideas how to avoid the second call to initalize_module when I run as a >>> service ? > > >>You can't avoid the second call but there are ways to gracefully handle it. Here is >>a snip of code from a module I developed a while back: >[...] >and I posted a patch which provides a generic API to do that. Since everybody is >replicating this code. And the thread has died w/o resolution. For some reason >http://marc.theaimsgroup.com doesn't have my original post, but only the rest of the >(unfinished) thread.
Stas, Since the work arounds (such as Bill suggested) are required for 1.3 and 2.0 compatiblity already, it seems we should focus on 2.1 and solve this for good. We have a new facility, ap_mpm_query, which would be perfect for answering nuggets of wisdom such as; * Running as a win32 service? Or detached console daemon? * A parent process? (Pre-fork or never forking (e.g. win32?) * Pre-startup config testing? * Server generation? (This answers the 2nd, 3rd, 4th startup pass question) These sorts of answers are useful to alot of modules, but we don't need a new callback to add them - simply build upon the ap_mpm_query() options. Bill
