Martin Lichtin wrote: > > [EMAIL PROTECTED] writes: > > Synopsis: Modules are initialized twice at startup. > > > > State-Changed-From-To: open-closed > > State-Changed-By: marc > > State-Changed-When: Mon Jun 1 15:55:49 PDT 1998 > > State-Changed-Why: > > > > Modules are supposed to be initialized twice, and they have > > been for a long time and will be for the forseeable future > > in the 1.x code. > > > > I suspect your confusion comes from some third-party patch > > you applied to your 1.2.x code that makes initialization only > > happen once. > > Right. It was added by the SSL patch. I'm surprised.
It is, indeed. > > Note that doing so can break some modules that > > rely on it happening twice. > > Unfortunately, I couldn't find documentation on that behaviour, it > doesn't make sense to me to call the initializers twice, what's the > reason? The justification I was given, a long time ago, was that modules are reinitialised on a server restart (i.e. SIGHUP or SIGUSR1) so they may as well go wrong at startup if they can't deal with that. I believe that that is just a rationalisation, though. The real reason is that it is simpler to let it do it that way. Cheers, Ben. -- Ben Laurie |Phone: +44 (181) 735 0686| Apache Group member Freelance Consultant |Fax: +44 (181) 735 0689|http://www.apache.org/ and Technical Director|Email: [EMAIL PROTECTED] | A.L. Digital Ltd, |Apache-SSL author http://www.apache-ssl.org/ London, England. |"Apache: TDG" http://www.ora.com/catalog/apache/ WE'RE RECRUITING! http://www.aldigital.co.uk/recruit/
