ID: 21783
Comment by: phyre at rogers dot com
Reported By: danielc at analysisandsolutions dot com
Status: Open
Bug Type: Documentation problem
Operating System: Any
PHP Version: 4.3.0
New Comment:
I note that there are different files (php-cli.ini) which isn't
documented as far as I can tell. That's for that pointer folks.
However, I believe that different directories are also quite
important. Apache php.ini goes with apache config. CLI should go in
/etc. Thoughts?
Previous Comments:
------------------------------------------------------------------------
[2003-02-02 06:44:17] [EMAIL PROTECTED]
Information found in bug #22001 should be included when this bug report
is dealt with:
http://bugs.php.net/22001
Pretty interesting stuff.
------------------------------------------------------------------------
[2003-01-20 21:25:40] danielc at analysisandsolutions dot com
The text I'd suggest is something along these lines. I don't know the
complete inner workings of PHP, so tweak it to reflect reality.
On Unix systems, PHP uses the php.ini file specified when PHP was
compiled. On Windows systems, PHP uses the php.ini from the same
directory as the php.exe file you execute. This behavior can be
modified by using the -c switch or by setting the PHPRC environment
variable. See the <a href="configuration.php">Configuration</a> page
for more information.
Thanks,
--Dan
------------------------------------------------------------------------
[2003-01-20 21:05:31] [EMAIL PROTECTED]
On a related note, I heard rumors that as of 4.3.0 ini files such as
php-cli.ini and php-cgi.ini are looked for first, is this true? If not
found, php.ini is looked for.
------------------------------------------------------------------------
[2003-01-20 20:52:26] [EMAIL PROTECTED]
Point taken :)
A cross reference to the info about the location of php.ini file
(/manual/en/configuration.php#configuration.file) should be inserted on
features.commandline page.
------------------------------------------------------------------------
[2003-01-20 20:46:58] danielc at analysisandsolutions dot com
Thank you for that link. None the less, people reading the
features.commandline.php won't necessarily read the configuration.php
page.
Gee, take me for example! :) I spent a significant amount of time
trying to figure out what was going on. Checked the command line page
in the manual, all of the user comments, the newsgroup archives and the
bug database. All of which turned up nothing, hence my bug report.
So, a simple mention of the situation and a cross reference link to
configuration.php would be helpful.
Heck, I'm fairly PHP literate and a good sleuth, but wound up using
your time anyway. This minor documentation tweak will save everyone
grief in the long run.
Of course, I could add a user comment, but that doesn't have the same
impact.
Thanks for your consideration,
--Dan
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/21783
--
Edit this bug report at http://bugs.php.net/?id=21783&edit=1
--
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
