ID: 43184
Updated by: [EMAIL PROTECTED]
Reported By: trustpunk at gmail dot com
-Status: Open
+Status: Feedback
Bug Type: CGI related
Operating System: Windows
PHP Version: 5.2.5RC2
New Comment:
Thank you for this bug report. To properly diagnose the problem, we
need a short but complete example script to be able to reproduce
this bug ourselves.
A proper reproducing script starts with <?php and ends with ?>,
is max. 10-20 lines long and does not require any external
resources such as databases, etc. If the script requires a
database to demonstrate the issue, please make sure it creates
all necessary tables, stored procedures etc.
Please avoid embedding huge scripts into the report.
Previous Comments:
------------------------------------------------------------------------
[2007-11-05 18:36:27] trustpunk at gmail dot com
It's PHP because my Mac outputs a similar error. The only difference
between the Windows and Mac is that the Mac outputs a Broken Pipe
instead of the original error Windows outputs.
<!---CGI LOG--->
05/Nov/2007:13:31:25 -0500 SUID: 0 PUID: 0 RUID: 0 URI: Reading 0
bytes failed = Broken pipe
05/Nov/2007:13:31:25 -0500 SUID: 0 PUID: 0 RUID: 0 URI:
timeout-header2!
<!---END OF CGI LOG--->
------------------------------------------------------------------------
[2007-11-05 15:30:51] crescentfreshpot at yahoo dot com
http://support.microsoft.com/kb/890015
------------------------------------------------------------------------
[2007-11-03 19:49:02] trustpunk at gmail dot com
Description:
------------
I don't have any errors in my PHP code but I see that in my CGI log, I
have this weird error. This shows up with every PHP release I download.
Reproduce code:
---------------
Just run a few PHP pages on your server and you will get the nasty
error
posted below in your CGI log file.
Note: This happens every time a new instance of "php-cgi.exe" is
started.
<!---CGI LOG--->
03/Nov/2007:15:30:45 -0500 SUID: 0 PUID: 0 RUID: 0 URI: Reading 0
bytes failed = The process cannot access the file because it is being
used by another process.
03/Nov/2007:15:30:45 -0500 SUID: 0 PUID: 0 RUID: 0 URI:
timeout-header2!
Expected result:
----------------
I don't want to see that error in my CGI log file again. What is going
on?
Actual result:
--------------
<!---CGI LOG--->
03/Nov/2007:15:30:45 -0500 SUID: 0 PUID: 0 RUID: 0 URI: Reading 0
bytes failed = The process cannot access the file because it is being
used by another process.
03/Nov/2007:15:30:45 -0500 SUID: 0 PUID: 0 RUID: 0 URI:
timeout-header2!
<!---End of CGI LOG--->
It never stops! It just keeps logging that garbage every few requests.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=43184&edit=1
