Hi Tom,
Did you ever get this problem solved?
I'm fighting the same issue - and if no better solution present it self,
I'm going
to do it by accessing a file of my choise. If the file doesn't exist -
create it and we
know we are in the first call. If it does exist - delete it, and we know
this is
The best I ever came up with was doing what your saying but instead of using a
file I used an environment variable, it's still a mess but I think its probably
cleaner and safe than using file locking. I would still be interested if you
ever did find a proper solution though,
Sorry I can't help
I had already assumed what Pete said was happening was happening, but I still
don't know how to tell whether I'm in the first one (apache test) or the second
(real init). Any ideas?
Tom
On Wed, 21 Aug 2002, you wrote:
Hi,
I asked about this a few weeks ago with apache on windows.
The
Hi,
I asked about this a few weeks ago with apache on windows.
The best answer I got was from George Schlossnagle:
quoteI believe this is because when apache does it's intial configtest run
as
part of start (to validate it's config), it has to do a complete startup
(otherwise it wouldn't know
--- Tom Oram [EMAIL PROTECTED] wrote:
Hi,
Can someone please answer my question?
When running a PHP extension when PHP is running as an apache module on linux
it's module init function (PHP_MINIT_FUNCTION) gets called twice, once before
apache forks then once after, is there any way of
On Thu, 15 Aug 2002, you wrote:
--- Tom Oram [EMAIL PROTECTED] wrote:
Hi,
Can someone please answer my question?
When running a PHP extension when PHP is running as an apache module on linux
it's module init function (PHP_MINIT_FUNCTION) gets called twice, once before
apache forks then
