ID: 21250
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
-Status: Open
+Status: Closed
Bug Type: Output Control
Operating System: OpenBSD 3.0
PHP Version: 4.3.0
New Comment:
imlicit_flush and output_buffering are two unrelated things, but this
fact has been known to confuse even seasoned php developers :)
In 4.3.0 you can have php-cli.ini (or php-{sapi}.ini) which can help
configure different sapi's in different ways.
Previous Comments:
------------------------------------------------------------------------
[2002-12-28 12:00:52] [EMAIL PROTECTED]
Thanks for pointing that out, though it wasn't the problem.
The CLI documentation leads one to believe that, by default, the PHP
CLI binary will override implicit_flush in the php.ini. This does not
seem to be the case. Making a new copy of php.ini in a different
directory and setting implicit_flush=On (along with
output_buffering=Off for good measure) did the trick.
Bug? Incorrect documentation? Even more user stupidity? :)
------------------------------------------------------------------------
[2002-12-28 11:21:01] [EMAIL PROTECTED]
Check your php.ini, you probably have output buffering enabled.
------------------------------------------------------------------------
[2002-12-28 11:19:46] [EMAIL PROTECTED]
A script that I have which automates the building of Apache + PHP +
ModSSL is showing strange behavior with PHP 4.3.0.
This script works fine with 4.2.x (CGI), but as soon as I upgraded to
4.3.0 (CLI), all output from echo is blocked until the commands that I
run through my many calls to system() are complete. The new CLI docs
say that implicit flush is on by default with the CLI, but when using
system(), exec(), or backticks this doesn't seem to be the case.
My apologies if this is mere user stupidity.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=21250&edit=1
