Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:28928
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain ioplex.com from 66.220.1.142 cause and error)
Date: Thu, 19 Apr 2007 23:46:08 -0400
To: internals@lists.php.net
Message-ID: <20070419234608.32e31f61.mba2000@ioplex.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Unexpected Extension Deinitializing on Startup
From: mba2000@ioplex.com (Michael B Allen)

Is there an Apache or PHP setting that would cause an extension to be
deinitilized in the initial root process on startup?

We have an extension that forks a process from the initial Apache root
process and does privileged work. The regular Apache workers running as
'apache' communicate with this root process using a pipe and shared
memory. We need that root process running.

Anyway, I have a customer who is seeing the extension initialize,
everything starts up great, and then the extension deinitialization
routine is called. For any other extension this behavior probably goes
unnoticed because (I suspect) the Apache worker processes do not see the
deinitializtion. Only the root process (not sure about that).  But for
our extension, we need the root process working so the deinitialization
kills our extension.

Is there some kind of Apache process model setting or something like
that or a bug that could cause the deinitialization routine to run?

Env is CentOS 4.4 with stock packages (PHP 5.1.6).

Any help with this would be greatly appreciated.

Mike

-- 
Michael B Allen
PHP Active Directory Kerberos SSO
http://www.ioplex.com/