Re: Mod Deinit Not Called if Bad Cmdline Option

From: Date: Tue, 13 Jun 2006 07:08:23 +0000
Subject: Re: Mod Deinit Not Called if Bad Cmdline Option
References: 1 2 3  Groups: php.internals 
Request: Send a blank email to internals+get-24105@lists.php.net to get a copy of this message
On Tue, 13 Jun 2006 05:45:26 +0200 "Steph Fox" <steph@zend.com> wrote: > Actually it's not true either... what made you think that, Michael? Care to > describe what you're seeing? Consider the following php script: #!/usr/bin/php -q -c foo <?php ... Apparently -c is a bad option because the script just prints usage and exits. Now, I have an extension that writes a message to a log file when it initializes and when it deinitializes. When the said script runs the initialization message is logged. When the script runs normally (no bad option) the deinitialization message is logged. When the script exits prematurely due to a bad command option, the deinitialization routine is not logged. This leads me to believe the deinitialization routine is not running. Perhaps it is or perhaps the script is being killed. Mike -- Michael B Allen PHP Extension for SSO w/ Windows Group Authorization http://www.ioplex.com/

« previous php.internals (#24105) next »