ID: 17265
Comment by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Closed
Bug Type: Scripting Engine problem
Operating System: FreeBSD4.5
PHP Version: 4.1.2
Assigned To: zeev
New Comment:
If this was really fixed, then Bug #17774 would also be fixed ?
Previous Comments:
------------------------------------------------------------------------
[2002-09-19 11:11:22] [EMAIL PROTECTED]
Issue (1) should be fixed.
As for issue (2) - it should be working fine. Note that disconnected
links are only detected while PHP sends out output. If you have a
script that just performs computations and doesn't emit output while
doing that, PHP has no way of detecting that the connection was closed.
------------------------------------------------------------------------
[2002-09-19 06:49:25] [EMAIL PROTECTED]
Ive been updating my version of PHP every week in the hope that this
problem is fixed.
alas, it still does not work.
Has anyone any feedback on this bug, when it may be fixed?
------------------------------------------------------------------------
[2002-09-05 15:56:57] [EMAIL PROTECTED]
Another one for Zeev to fix.. :)
------------------------------------------------------------------------
[2002-09-05 13:42:59] [EMAIL PROTECTED]
This bug is trivially reproduceable with the following code fragment:
while (1) {
sleep(3);
$status = connection_status();
syslog(1, "connection status is $status");
$status = connection_aborted();
syslog(1, "connection aborted is $status");
}
It happens consistently using php4.1.2 compiled under OpenBSD 2.8.
If you watch the error log, the connection_status() always returns 0,
whether or not the stop button has been pressed. Similarly,
connection_aborted() always returns 0.
------------------------------------------------------------------------
[2002-06-07 20:53:02] [EMAIL PROTECTED]
the functions do work if you hve a sleep() with more then one second
everything below don't work.
some one should fix that bug
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/17265
--
Edit this bug report at http://bugs.php.net/?id=17265&edit=1
