iis + php installation

iis + php installation

Hello

I have win 2003 and iis 6.0. I have tried to install PHP 5 (the newest 
vesrion). I have followed the steps described in the php manual and 
everything seems to be working right. But I have the following major problem.

I have a php page called phpinfo.php where I call the phpinfo(). When I 
change php.ini the contents of this page don't change, actually they remain 
the same as the default php.ini values. However if I do on command prompt 
php -i
then I see that the changes that I made are applied.

Do you have any idea what that might be? The problem is that I want to turn 
on the mysql support. In the command prompt output the mysql support is 
activated. However it's not activated in the phpinfo html output.

Thanks

date: Sat, 13 Oct 2007 00:25:01 -0700 author: ibob05

Re: iis + php installation

On Oct 13, 12:25 am, ibob05  wrote:
> Hello
>
> I have win 2003 and iis 6.0. I have tried to install PHP 5 (the newest
> vesrion). I have followed the steps described in the php manual and
> everything seems to be working right. But I have the following major problem.
>
> I have a php page called phpinfo.php where I call the phpinfo(). When I
> change php.ini the contents of this page don't change, actually they remain
> the same as the default php.ini values. However if I do on command prompt
> php -i
> then I see that the changes that I made are applied.
>
> Do you have any idea what that might be? The problem is that I want to turn
> on the mysql support. In the command prompt output the mysql support is
> activated. However it's not activated in the phpinfo html output.
>
> Thanks

Sounds like a PHP issue.

It could depend on how/when PHP reads php.ini.

IIS loads an ISAPI DLL once on startup and unloads it on restart. So,
if you are using the ISAPI version of PHP, UNLESS PHP has Windows-
specific code to take advantage of FileChangeNotifications to read
your php.ini updates when you make them, or re-read PHP.INI on every
request (bad performance idea), the ISAPI version will likely not
dynamically notice changes to php.ini

Meanwhile, IIS loads and unloads PHP CGI EXE for every single request
(very inefficient on Windows), but on load it will read in php.ini and
so probably notices the php.ini changes when it starts, just like it
does on the commandline.

If this is the reason, this is more of a problem with PHP and how it
fails to detect changes to its configuration that you expect it to
detect. In many senses, this problem is due to a common PHP codebase
supporting both Windows and *nix because *nix FileSystems commonly do
not support advanced features like FileChangeNotifications that NTFS
does.

//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

date: Sat, 13 Oct 2007 09:58:10 -0000 author: David Wang

Re: iis + php installation

"David Wang" wrote:

> Sounds like a PHP issue.
> 
> It could depend on how/when PHP reads php.ini.
> 
> IIS loads an ISAPI DLL once on startup and unloads it on restart. So,
> if you are using the ISAPI version of PHP, UNLESS PHP has Windows-
> specific code to take advantage of FileChangeNotifications to read
> your php.ini updates when you make them, or re-read PHP.INI on every
> request (bad performance idea), the ISAPI version will likely not
> dynamically notice changes to php.ini

What you write seems reasonable, I 'll probe at php.net also. However I have 
both restarted iss and the machine with no success...

date: Sat, 13 Oct 2007 06:40:00 -0700 author: ibob05

Re: iis + php installation

On Oct 13, 6:40 am, ibob05  wrote:
> "David Wang" wrote:
> > Sounds like a PHP issue.
>
> > It could depend on how/when PHP reads php.ini.
>
> > IIS loads an ISAPI DLL once on startup and unloads it on restart. So,
> > if you are using the ISAPI version of PHP, UNLESS PHP has Windows-
> > specific code to take advantage of FileChangeNotifications to read
> > your php.ini updates when you make them, or re-read PHP.INI on every
> > request (bad performance idea), the ISAPI version will likely not
> > dynamically notice changes to php.ini
>
> What you write seems reasonable, I 'll probe at php.net also. However I have
> both restarted iss and the machine with no success...

Restarting IIS and the machine will have no effect on what is
essentially a PHP design flaw that I describe because it doesn't do
anything to address the flaw. Fixing PHP will be the only way for it
to have the behavior you expect.

Another thought -- PHP supports multiple locations for its PHP.INI
file. Perhaps you are changing one PHP.INI file but the way you've
configured PHP in IIS causes it to read another.

In any case, these are all PHP questions/issues or user configuration
caused problems. Not problems with IIS.

//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

date: Sun, 14 Oct 2007 01:27:01 -0000 author: David Wang