#20015 [Opn]: session.auto_start diables flushing output
| From: | amir at abiri-e dot com | Date: | Mon, 21 Oct 2002 21:21:08 +0000 |
| Subject: | #20015 [Opn]: session.auto_start diables flushing output | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-22994@lists.php.net to get a copy of this message | ||
ID: 20015
User updated by: amir@abiri-e.com
Reported By: amir@abiri-e.com
Status: Open
Bug Type: Output Control
Operating System: Linux Redhat 7.2
PHP Version: 4.2.3
New Comment:
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.
Previous Comments:
------------------------------------------------------------------------
[2002-10-21 16:13:23] amir@abiri-e.com
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