Re: [PHP-DEV] CLI and php.ini

2002-02-20 Thread J Smith
To a certain extent, but it doesn't work well at all. And it isn't portable. For instance, when I use this on my machine (linux, 2.4.9 kernel) #!/usr/local/bin/php -c /path/to/ini -q The path is set to " /path/to/ini -q", with a leading space and the -q. If I try this: #!/usr/local/bin/php -

Re: [PHP-DEV] CLI and php.ini

2002-02-19 Thread Shane Caraveo
Hmm, actually -c takes a path. - Original Message - From: "brad lafountain" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, February 19, 2002 4:47 PM Subject: Re: [PHP-DEV] CLI and php.ini > > The magic > #!/usr

Re: [PHP-DEV] CLI and php.ini

2002-02-19 Thread brad lafountain
The magic #!/usr/local/bin/php -c local.ini already works - brad --- J Smith <[EMAIL PROTECTED]> wrote: > > From what I understand, starting with PHP 4.2.x, PHP is going to > automatically build with a CLI executable by default. This means that even > when you install as, say, an Apache

[PHP-DEV] CLI and php.ini

2002-02-19 Thread J Smith
>From what I understand, starting with PHP 4.2.x, PHP is going to automatically build with a CLI executable by default. This means that even when you install as, say, an Apache SAPI module, you're still going to get the CLI, correct? That being the case, a few months ago a thread popped up ab