Date: Sun, 13 Jun 2004 10:38:32 -0500 From: Kirk Strauser <kirk@strauser.com> To: Matthew Seaman <m.seaman@infracaninophile.co.uk> Cc: freebsd-questions@freebsd.org Subject: Re: Weird processes after upgrading to apache2 Message-ID: <87y8mrmps7.fsf@strauser.com> In-Reply-To: <20040613091625.GC75168@happy-idiot-talk.infracaninophile.co.uk> (Matthew Seaman's message of "Sun, 13 Jun 2004 10:16:25 %2B0100") References: <87acz8ndnv.fsf@strauser.com> <20040613091625.GC75168@happy-idiot-talk.infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-=-= Content-Transfer-Encoding: quoted-printable At 2004-06-13T09:16:25Z, Matthew Seaman <m.seaman@infracaninophile.co.uk> w= rites: > I suspect it's mod_perl causing the weirdness. Plain apache-2.0.49 works > perfectly well for me serving up static html and some php. > > mod_perl is unusual though in that it has such a complete interface to the > apache API. I don't doubt that you can cause any of the effects you've > seen with unsuitably written perl code. Serious debugging time required. I temporarily disabled mod_perl and the "problems" went away as expected. I'm kind of surprised that I never saw these problems with the same web application (TWiki) and mod_perl on Apache 1, but it seems to be unique to my Apache 2 installation. Weird. Anyway, the server is question has enough muscle to serve TWiki pages quickly, so I may semi-permanently ditch mod_perl. =2D-=20 Kirk Strauser --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBAzHT45sRg+Y0CpvERAkauAJ9G+NQPMjEMrYE+mUB7H9J5Q3C0aACfdJ+B zv5JUp+xcgDn6oPb/PE2IqM= =BuUC -----END PGP SIGNATURE----- --=-=-=--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87y8mrmps7.fsf>