Re: [SM-USERS] Why is it so S-L-O-W ?

[Konstantin R. <ic...@du...>]

On Fri, 2002-03-29 at 13:13, John Madden wrote:
> > I would also not recommend compiling apache/php from source -- it would
> > hardly solve anything and make your upgrades a lot more complicated.
>=20
> Case in point: If `http -l` shows no mod_php, they're using the CGI versi=
on
> of PHP.  Given this fellow's hardware and the speed of IMAP with regular
> clients, the web server appears to be the bottleneck.  That's just
> deduction...

There are two versions of php that come with redhat's php package. One
is a cgi, and another is a mod_php. If you do "rpm -ql php" you will
notice the following files:

/usr/bin/php
/usr/lib/apache/libphp4.so

The first one is a cgi, and the second one is a mod_php shared object.
The advantage of this is that you can use php in shell scripts should
you need to do so, or allow users to use ~username/*.php files and run
them as that user -- something that can't be done with mod_php.

Moreover, running "httpd -l" will only show you modules that were
compiled INTO apache, not shared objects. Hence, it outputs the
following on a Red Hat system:

icon@norbert:[~]$ httpd -l
Compiled-in modules:
  http_core.c
  mod_so.c
suexec: enabled; valid wrapper /usr/sbin/suexec

mod_so.c module provides hook-ups for shared modules, which are loaded
namely from httpd.conf from .so files in /usr/lib/apache.

Therefore the aforementioned statement that "httpd -l" shows you if you
have a cgi or mod_php version of PHP is erroneous.

The summary:
- Your apache runs mod_php
- Don't recompile apache and php from source
- Look for problems elsewhere.

--=20
 0>  Konstantin ("Icon") Riabitsev
/ )  Duke University Physics Sysadmin
 ~   www.duke.edu/~icon/pubkey.asc