By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,722 Members | 1,247 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,722 IT Pros & Developers. It's quick & easy.

CLI and Apache API have differrent config statements

P: n/a
Hello,

Executing phpinfo() from the command line and on the browser reveal
that the CLI and Apache API have different config statements. How
would I resolve this? I would like the CLI API to have the same config
as the Apache API.

Your advice will be greatly appreciated.

Thanks,

Andrew Pasetti
Jul 17 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Hi,

Andrew Pasetti wrote:
Hello,

Executing phpinfo() from the command line and on the browser reveal
that the CLI and Apache API have different config statements. How
would I resolve this? I would like the CLI API to have the same config
as the Apache API.


do you have compiled php after you installed it from another source?
Meaning: In my case I run a SuSE Linux and installed the php rpm.
Afterwards I compiled a newer version of php from the source.
if I run the info.php from the command line, the originally installed cli is
used (from /usr/bin/). The cli resulting from my compile is
in /usr/local/bin
so maybe try to call this one directly.

HTH

Michael
Jul 17 '05 #2

P: n/a
On 15 Oct 2004 13:21:54 -0700, an***********@yahoo.com (Andrew Pasetti) wrote:
Executing phpinfo() from the command line and on the browser reveal
that the CLI and Apache API have different config statements. How
would I resolve this? I would like the CLI API to have the same config
as the Apache API.


It would seem then that the PHP executable and the PHP DLL are from separate
compilations/installs. Assuming that PHP Apache support is a via a loadable
module, it's worth checking timestamps on the two - mod_php4.so and the php
executable. Could you perhaps have multiple PHP installs? e.g. /usr/bin/php ,
/usr/local/bin/php ?

The easiest way to resolve this is probably just to compile & install again,
making sure all the paths are where you expect (i.e. set --prefix during
configure as appropriate).

--
Andy Hassall / <an**@andyh.co.uk> / <http://www.andyh.co.uk>
<http://www.andyhsoftware.co.uk/space> Space: disk usage analysis tool
Jul 17 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.