php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Doc Bug #24657 php.ini location different for CLI
Submitted: 2003-07-14 23:10 UTC Modified: 2003-07-15 02:16 UTC
From: phyre at rogers dot com Assigned:
Status: Not a bug Package: Documentation problem
PHP Version: 4.3.2 OS: Linux
Private report: No CVE-ID: None
View Developer Edit
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: phyre at rogers dot com
New email:
PHP Version: OS:

 

 [2003-07-14 23:10 UTC] phyre at rogers dot com 
Description:
------------
So, as many people I'm sure do, I require much different options (ie: safe mode, etc) for running under my web server than running from the command line, yet I can only choose one ini file.  Various add-ons such as ZendDebugger I don't like starting up from the CLI.

  I assume it wouldn't be hard to add a --with-cli-config-file-path which works for the CLI only?

I place php.ini in my apache config directory, which has restrictive rights.  Hence, an end user can't load it.  So PHP needs to be compiled in two pieces (I need to then make another build and ONLY install the CLI).

  Seems like this could be a simple fix and it seems to make sense.  By default, it should point to the normal config path (--with-config-file-path).

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2003-07-15 00:59 UTC] derick@php.net 
I'm marking this as a documentation problem, as you can use php-cli.ini for specific settings for CLI. (Actually you can use php-<sapiname>.ini). I couldn't find docs for this though on line.
 [2003-07-15 01:01 UTC] helly@php.net 
man php
 [2003-07-15 01:16 UTC] philip@php.net 
Duplicate of:
http://bugs.php.net/bug.php?id=21783
 [2003-07-15 02:16 UTC] sniper@php.net 
Please do not submit the same bug more than once. An existing
bug report already describes this very problem. Even if you feel
that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments
to the existing bug instead.

Thank you for your interest in PHP.

..
 
PHP Copyright © 2001-2025 The PHP Group
All rights reserved. 		Last updated: Fri May 09 21:01:27 2025 UTC