ID: 9422
Updated by: sbergmann
Reported By: [EMAIL PROTECTED]
Old-Status: Open
Status: Feedback
Bug Type: Apache related
Operating system: 
PHP Version: 4.0.4
Assigned To: 
Comments:

Are you loading non-thread-safe PHP Extensions in your php.ini? Does this problem 
persist with PHP 4.0.5?


Previous Comments:
---------------------------------------------------------------------------

[2001-03-31 19:06:17] [EMAIL PROTECTED]

No, plain apache goes into standby. 

I tested apache 1.3.19 with php 4.0.5RC1 from www.php4win.de (phpinfo looks a little 
bit hacked?), no standby.

Tested it with php cgi (3.1.17, 4.04, 4.0.5RC1) when a longer script is running, win 
goes standby after php timeout killed the script (which is a good idea I think). 

My guess is in module version something is not ending, even without a current script 
running?

Gustav Graf


---------------------------------------------------------------------------

[2001-03-31 09:16:34] [EMAIL PROTECTED]
Does it happen with plain Apache (without PHP)? If not, could you try with 1.3.19 and 
newer version of PHP?

---------------------------------------------------------------------------

[2001-03-17 19:27:17] [EMAIL PROTECTED]
same with Sambar Server 4.4

---------------------------------------------------------------------------

[2001-02-23 10:43:53] [EMAIL PROTECTED]
If PHP 4.04 is included in Apache 1.3.17 as module with:

LoadModule php4_module c:/php/sapi/php4apache.dll
AddType application/x-httpd-php .php

and Win goes into standby the standby window and the Apache console freezes, omnly 
after after killing the second apache task - with small letters - computer goes 
standby.

Gustav Graf

---------------------------------------------------------------------------



ATTENTION! Do NOT reply to this email!
To reply, use the web interface found at http://bugs.php.net/?id=9422&edit=2


-- 
PHP Development 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]

Reply via email to