On Thursday 24 May 2001 13:30, Asendorf, John wrote: > For those of us running IIS, the instructions say to follow the php.exe > setup in the CGI mappings as %s %s... Obsolete instructions which will magically have disappeared with the 4.0.6 release. I guess that IIS knows how to fire up php and pass it the script filename without any help from the %s's. You can safely get rid of them. > I'm wondering if it is causing incorrect URLs to not allow an instance of > php.exe to shut down. i.e., when someone type in an incorrect URL that > ends in .php, they get a CGI error instead of a 404, at this point, it > doesn't seem to allow php.exe to shut down... so every now and then I have > to restart the server so that I can get rid of the bad instances in the > task manager (which won't allow me to shut them down (Access Denied) even > with the w3 service shut down...) Someone else mentioned ticking the 'check file exists' box which will cause IIS to send a 404 before it asks php to open a file which does not exist (and as a useful by product, will handle authentication based on NTLanMan file permissions on your behalf). This facility *is* available on IIS4. The cgi error you get otherwise is just IIS complaining that it received no output from PHP. Maybe the zombie PHPs are just hanging around waiting for a sript to appear? In any event, the reason you can't kill the zombies with task manager is that it doesn't have permission to kill them as it normally runs as the logged in user, but it actually needs to run on a system account. You can make it do that by using the at command: at <timerealsoonnow> taskmgr When it gets to timerealsoonnow, task manager will pop up and will be able to kill off your zombies. Cheers -- Phil Driscoll -- PHP Windows Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
