|
|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
Get inside! Sample the range of functionality easily built with JMSL Library for Time Series Data Analysis, Heat Maps, Portfolio Optimization, Monte Carlo Simulation, Stock Price Charting and more. Download Now! |
|
#1
|
|||
|
|||
|
Setup problems?
How can I setting up the apache+php, in the way that, php is a CGI interpreter?
and also, can I setting up the php to been a cgi interpreter and apache module at the same time. Lastly, if I can, how does the apache, distinguish which php file should parsed by CGI interperter and which PHP file parsed by apache module?? |
|
#2
|
|||
|
|||
|
>> in the way that, php is a CGI interpreter?
Just don't specify --with-apache or --with-apxs. e.g: --prefix=/usr/local --with-config-file-path=/usr/local/etc/php --disable-pear --enable-versioning --with-system-regex --enable-track-vars >> can I setting up the php to been a cgi interpreter and... Yes. Many UNIX systems come with Perl preinstalled. Does that mean they can't install mod_perl? No. >> distinguish which php file should parsed by CGI interperter Put PHP CGI scripts in your ScriptAlias'ed cgi-bin, or name those scripts with .cgi extension for execution outside of cgi-bin. Keep in mind that a CGI script doesn't always be Perl, it could be python, shell, TCL, bash or any others. Another signaficant difference is that, you chmod your CGI scripts to be executable, you don't chmod 755 to your PHP script as Apache module. Last edited by freebsd : June 25th, 2001 at 07:00 PM. |
![]() |
| Viewing: Dev Shed Forums > System Administration > Apache Development > Setup problems? |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|