OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Saad Kadhi (Tech Accnt) (bsdguynoos.fr)
Date: Sat Feb 10 2001 - 04:50:09 CST

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    Hi there Charles,

    Charles D. Burgess wrote:

    > --- Stoyan Genov <sdgorion.rila.bg> wrote:
    >
    >> Hi,
    >>
    >> [Charles wrote]
    >>
    >>> If apache is installed already. How do I get rid of it to compile
    >>
    >> it with php?
    >>
    >> If I am getting this correct, you do NOT want to compile apache
    >> again, but you
    >> DO want to compile php as a module to the existing apache
    >> instalation.
    >>
    >> In this case, you can use the --with-apxs option of the php configure
    >> script. Assuming apxs is in your $PATH, everything should be just
    >> fine.
    >> At least was for me :)
    >>
    >> -Stoyan Genov
    >>
    >> All:
    >
    > Ok. so I think what I've learned is that really I have 2 options. I can
    > either use the DSO suppor already in my existing apache or I can go
    > with the traditional statically compiled in method. I dont have a lot
    > of traffic and cant really see myself having a lot of traffic but....I
    > want to be able to handle a lot..as a learning experience. So I guess
    > what I am asking now is for an opinion(or fact). Which way is better
    > performance wise?
    > I still need to read up on the FLAVORS+.
    I think that a compiled-in module is faster than DSO and may handle a lot. At least, it avoids the overhead involved in module loading.

    I myself compile Apache + PHP as a module from the source & install them
    in the same directories as the default one that comes w/ OpenBSD (& I
    use the mysql port) coz I need to serve a lot of PHP pages.

    Regards,

    -- 
    ### Saad Kadhi -- Network & Security Engineer ###
    \|/ ____ \|/
    ~-/ oO \-~
    /_( \__/ )_\
        \__U_/