ID: 20015 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Open +Status: Feedback Bug Type: Output Control Operating System: Linux Redhat 7.2 PHP Version: 4.2.3 New Comment:
Please try using this CVS snapshot: http://snaps.php.net/php4-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-latest.zip Previous Comments: ------------------------------------------------------------------------ [2002-10-21 16:21:07] [EMAIL PROTECTED] also setting "-d session.auto_start=0" in the binary command line in the first line of the script doesn't solve the problem, yet doing so when calling the script in the "php [script name]" form from the shell does. in both cases setting the entry in the ini file solves the problem completely. ------------------------------------------------------------------------ [2002-10-21 16:13:23] [EMAIL PROTECTED] I'm not sure this is indeed a bug, I tried looking for some piece of documentation about this, but failed. I wrote a script that used the flush() command and it failed to operate correctly. knowing the many possible pitfalls around output buffering, and since the role of the script is a web-crawler anyway, I moved it to the cli version, yet the problem persisted - the script (which is meant to work for hours) refuses to flush it's output, no matter what I did. After going over the ini file line by line commenting and uncommenting, I found that "session.auto_start = 1" causes php to fail any form of output buffer flushing: flush(), ob_flush() and implicit_flush directive, even with the cli sapi. I don't want to duplicate the ini file, therefore I would be happy to find a way to keep the apache module with session.auto_start=1, yet overcoming this issue, so to be able to flush my output, at least in cli scripts. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=20015&edit=1
