* Edin Kadribasic wrote:
> I'm curious: how would this affect hosted environments? When you use PHP as
> a module in Apache, the php.ini file is read when the server is started.
Hosters normally use PHP CGI environments.
--
PHP-Support * realitätsnahe Performance-Messungen mit Code-Analyse
> Please only remove CWD from php.ini search path when
> compiled as cli. (There are some hosters out there
> where you can have your own php.ini at your vhost
> which is IMHO a good feature.)
I'm curious: how would this affect hosted environments? When you use PHP as
a module in Apache, the php.
Hi,
* Edin Kadribasic wrote:
> Are there any objections to removing CWD from php.ini search path?
Please only remove CWD from php.ini search path when
compiled as cli. (There are some hosters out there
where you can have your own php.ini at your vhost
which is IMHO a good feature.)
--
PHP-Supp
> > Currently php searches for php.ini in the current working directory,
PHPRC
> > environment variable and the compiled in default dir (in that order).
> > Searching in the CWD first is IMHO not a very good thing, especially
when
> > dealing with cli scripts.
> >
> > Are there any objections to r
On Thu, Feb 14, 2002 at 04:53:56PM +0100, Edin Kadribasic wrote :
> Currently php searches for php.ini in the current working directory, PHPRC
> environment variable and the compiled in default dir (in that order).
> Searching in the CWD first is IMHO not a very good thing, especially when
> deal
