ID: 20642
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
-Status: Open
+Status: Closed
Bug Type: Feature/Change Request
Operating System: Linux GNU/Debian 3.0r0
PHP Version: 4.2.3
New Comment:
Just put
@ob_end_flush();
on top of your script. No need for changing ini settings.
Previous Comments:
------------------------------------------------------------------------
[2002-11-27 02:56:48] [EMAIL PROTECTED]
This might sound like bogus to you but for a professional environment
this certainly is NOT acceptable. As a programmer I know everything is
possible, it only depends on how much effort you put into it. You could
at least try to point out why you deny this change request instead of a
mere "no I can't".
------------------------------------------------------------------------
[2002-11-26 20:39:07] [EMAIL PROTECTED]
No, it can't.
------------------------------------------------------------------------
[2002-11-26 04:44:29] [EMAIL PROTECTED]
Hello,
I am writing a php shell script (as I do very often in crontabs and
procmail setups) only this time I use stdin/stdout for user interaction
with the script. The only problem is that output_buffering defaults to
4096 which results in a script that is really not workable since there
is no screen output (output < 4096). Also the flush() command is no
help (I still get nothing, I don't know whether this is a bug or a
result of an ini setting).
To fix this problem I can only change the php.ini value to 0 but this
is really not what I want since this is a server wide change. I'd
rather use ini_set("output_buffering","0") instead.
So my change request in short is, can the rights for altering the ini
variable output_buffering change from PHP_INI_PERDIR|PHP_INI_SYSTEM to
PHP_INI_ALL in future versions?
Jeroen
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=20642&edit=1
