Heya, thanks for testing.. I didn't use -r 'phpinfo();' since -i is supposed to do the same..
On Sun, 2003-11-02 at 00:33, Nathan Sullivan wrote: > /usr/local/php/bin/php -r 'phpinfo();' | grep implicit > implicit_flush => On => Off Now check this: /usr/local/php-4.3.3/bin/php -r 'phpinfo();' | grep implicit implicit_flush => On => Off /usr/local/php-4.3.3/bin/php -i | grep implicit implicit_flush => Off => Off What's happening here? ( same results for 4.3.2 and 4.3.1 on 3 different systems..) Let's check with some Testcode: running this simple code /usr/local/php-4.3.3/bin/php -r 'echo "test"; while (1);' I do not get any output. Which means for ME, the implicit_flush really IS off. When i create a simple test.ini ( just [PHP] implicit_flush=1 ) first and pass it along /usr/local/php-4.3.3/bin/php -c test.ini -r 'echo "test"; while (1);' i get the "test" and have the cursor sitting behind it.. since the loop obviously does NOT return.. Last but not least, i can reproduce that on ALL systems i have php on (all redhat linux based though), for version 4.3.1, 4.3.2 and 4.3.3. Due to the fact that my 5.0.0 installation currently segfaults (prolly some broken libs...) i cannot check it on php v5.. So either the docs are wrong or php-cli is broken ;) OR i do something wrong here i am unable to see... As of now, i still consider that a bug - the question remains though: PHP-CLI or php-DOC ;) > > /usr/local/php5/bin/php -r 'phpinfo();' | grep implicit > implicit_flush => On => Off > zend2.implicit_clone => no value => no value > > I think it does overwrite it :) Sounds like an issue with your PHP > installation to me. > > Nathan. > > On Sat, 01 Nov 2003 19:29:54 +0100, Arne Blankerts wrote > > Heya.. > > > > I just started messing around with CLI mode and found an > > inconsistency with the manual and actual behavior. Before i file a > > bug for that, let me know if where the bug actually is? > > > > According to the manual, CLI forces 'implicit_flush' to be 'TRUE' no > > matter what: > > > > (http://de.php.net/manual/en/features.commandline.php) > > "Note: These directives cannot be initialized with another value > > from the configuration file php.ini or a custom one (if specified)." > > > > To my tests with php-4.3.3 cli binary, this is NOT true. Neither is the > > setting forced to TRUE nor does it ignore the settings in the php.ini. > > > > So.. Is that a BUG in php or should the documentation be changed? CU! Arne -- The day microsoft creates something that doesn't suck, is the day they start to sell vacuum cleaners!
