#39274 [Opn->Fbk]: php.ini not being read
| From: | tony2001@php.net | Date: | Fri, 27 Oct 2006 07:59:55 +0000 |
| Subject: | #39274 [Opn->Fbk]: php.ini not being read | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-104054@lists.php.net to get a copy of this message | ||
ID: 39274
Updated by: tony2001@php.net
Reported By: campbell at neotext dot ca
-Status: Open
+Status: Feedback
Bug Type: *Configuration Issues
Operating System: Fedora Core 6
PHP Version: 4.4.4
New Comment:
Show us your phpinfo().
Previous Comments:
------------------------------------------------------------------------
[2006-10-27 07:50:05] campbell at neotext dot ca
yes. the config-file-path parm takes either or... I tried
that early on. I'm building a clean Core4 to try this on
and will let you know what happens. I'm thinking this
is a Fedora bug, but it his here.
------------------------------------------------------------------------
[2006-10-27 07:45:41] tony2001@php.net
--with-config-file-path=/etc/php.ini - this configure option accepts
DIRECTORY as its value.
------------------------------------------------------------------------
[2006-10-27 07:23:44] campbell at neotext dot ca
Same revs of apache, mysql and php, build similar build,
on FreeBSD 6.1-RELEASE behaves correctly.
D~
------------------------------------------------------------------------
[2006-10-27 07:11:27] campbell at neotext dot ca
Hi. I did it everywhichway.
Yes. Running phpinfo tells me where it is reading,
which is where I expect, but the parms in the ini
file are not being read.
I'm going to run the same build/install on clean core4 now
and see what happens...
Dhu
------------------------------------------------------------------------
[2006-10-27 07:10:36] campbell at neotext dot ca
Hi. I did it everywhichway.
Yes. Running phpinfo tells me where it is reading,
which is where I expect, but the parms in the ini
file are not being read.
I'm going to run the same build/install on clean core4 now
and see what happens...
Dhu
------------------------------------------------------------------------
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/39274
--
Edit this bug report at http://bugs.php.net/?id=39274&edit=1