Yup. The way i see it, is if you're going to run apache with PHP or PERL extensions anyway, then there's no need for it to be installed as a DSO. Might as well load it outright, when apache starts.
On Fri, 19 Apr 2002, Orlando Andico wrote: > On Fri, 19 Apr 2002, Andre John Cruz wrote: > .. > > by the way...which do you prefer, compiling apache with its PHP module > > as a DSO or statically compiling PHP with apache? is the performance hit > > associated with loading the DSO at runtime significant? > > I never compile anything as DSO. There are weird interactions in mod_perl > when it's loaded as a DSO, interactions that you do NOT see until you're > doing fancy-schmancy stuff. > > This is why Red Hat gets away with building their Apache with mod_perl as > a DSO. When you get to the types of applications we're using (where Apache > bloats to an amazing 20-30MB per httpd) the DSO method just doesn't cut > it: weird segmentation faults at the most inopportune times. > > Oh well.. > > > --- > Orlando Andico <[EMAIL PROTECTED]> > Mosaic Communications, Inc. > > _ > Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph > To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] > > To subscribe to the Linux Newbies' List: send "subscribe" in the body to >[EMAIL PROTECTED] > _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
