RE: [PHP-WIN] What to do if PHP gets out of control on NT

---------------------------------------------------------------------------- ----------------- Disclaimer: The information contained in this email is intended only for the use of the person(s) to whom it is addressed and may be confidential or contain legally privileged information. If you are not the intended recipient you are hereby notified that any perusal, use, distribution, copying or disclosure is strictly prohibited. If you have received this email in error please immediately advise us by return email at postmaster@normandy.com.au and delete the email document without making a copy. ---------------------------------------------------------------------------- ----------------- Thanks for that Sasha, This makes sense :) -----Original Message----- From: Sasha Rudan [mailto:mprinc@aim.ac.yu] Sent: Monday, October 23, 2000 5:17 PM To: 'php-windows@lists.php.net' Subject: Re: [PHP-WIN] What to do if PHP gets out of control on NT "Nold, Mark" wrote: > Im running PHP as CGI ( www.php4win.de > <http://www.php4win.de> distro) on > Apache (not as a service) on NT 4 server. > > If i have a runaway PHP process i can see it in the task manager but i cant > kill it. I get told that i dont have permission (at the terminal with the > user who started the Apache app... which happens to be Administrator). This > is generally because of a bad script in development but its still a problem. > > So is there any way to kill these PHP processes? I can envisage if we go to > production with this and something goes wrong ill end up with PHP.exe's all > sitting on the task list. Actually, when Administrator starts Apache as service on NT server its owner is not administrator but SYSTEM (something like root on UNIX) and even administrator can't terminate SYSTEM's tasks. Also it's big security hole starting Apache as SYSTEM. I prefer creating new account apache without NETWORK privileges and just to read WEB Document Root Dir and write to apache config dir (i.e. d:/Program Files/Apache Group/Apache/confg ). After that you start Startup.... For Apache Services and set Account and password to just created account. Now when we notice some poor script, we should login on created account and kill it.