[lug] Bad Apache problem?

[Justin-lists]

I'm going to pass on backing out glibc. I've had my share of problems in the past when messing with the glibc package :) I did find this though when doing some more searching:
http://www.apache.org/dist/httpd/patches/apply_to_1.3.2/htaccess_check.txt

That is the same problem I am experiencing. But that patch was for a much older version of Apache. The problem was seemingly caused by PHP whereas in my case the problem appears to be caused by glibc shared libs. Yesterday I upgraded my openssl to the latest version and again recompiled my Apache and components from scratch. Problem still exists...

Justin

--
glow at jackmoves.com


---------- Original Message -----------
From: "D. Stimits" <stimits at attbi.com>
To: lug at lug.boulder.co.us
Sent: Wed, 26 Mar 2003 14:28:30 -0700
Subject: Re: [lug] Bad Apache problem?

> Justin-lists wrote:
> 
> > All my modules/additions to Apache were also rebuilt (mod_perl, 
> > mod_ssl, PHP, mm) during the compilation/rebuild of Apache. The 
> > 'AllowOverride' directive in Apache is part of the httpd_core though 
> > so that wouldn't matter anyways. Is it possible to back down glibc to 
> > the previous version? I'd like to do that just temporarily for 
> > testing. That would atleast prove whether or not glibc is the cause of 
> > this problem. Thanks.
> >
> > Justin
> >
> > --
> > glow at jackmoves.com
> 
> ...
> 
> I've never backed out on a glibc version, it's frightening at best 
> (scarier than Scary Movie). I know it can be done, but have a rescue 
> disk ready. Perhaps someone else here could give advice on the way 
> to back out to the old glibc version safely...it could be simple.
> 
> D. Stimits, stimits AT attbi DOT com
> 
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: lug.boulder.co.us port=6667 channel=#colug
------- End of Original Message -------