Erik Lotspeich wrote:
Hi William,
Thanks for your response.
Your *loadable* module doesn't survive to the end of the proc pool
because it's codepages were already unloaded. Be careful.
So is there a way for a dynamically-loadable module to do any teardown
when Apache quits? It seems that there must be some signal, API, or
mechanism.
Your module is unloaded at least twice, and then a 3rd, 4th, 5th time
upon restarts.
The conf pool represents the lifetime of that session. You get that as
the apr_pool_t * argument to your register_hooks callback.
Bill
