a=SERVER_CREATE(); b=SERVER_CREATE(); RegulateDatabase(a, ...); global_init(b); global_init(c);
I have no idea where 'c' is coming from--like I said, I've instrumented {SERVER,DIR}_{CREATE,MERGE}, which I think should cover everything.
PostConfig is called twice, because of the server startup:
http://perl.apache.org/docs/2.0/user/handlers/server.html#Startup_Phases_Demonstration_Module
Right...I figured I could probably handle that by setting a flag variable somewhere, or something of the sort.
Why are the PostConfig handlers being given config objects with different addresses, though?
...hmm. It looks like they're being handed different server objects: global_init server: Apache::Server=SCALAR(0x8caded0) global_init server: Apache::Server=SCALAR(0x8c059e0)
Okay, this is starting to beg a question: why is PostConfig called twice? What does each call represent? Why is it only called once for an 'apachectl -k restart'?
And perhaps the question I should've asked to start with: if I need to fork off one background process for the entire Apache server, what handler should I do so in?
-- Brent "Dax" Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker
Oceania has always been at war with Eastasia.
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
