Re: Problems with 5.0 upgrade and Apache

["menion?" <menion mindless com>]

Whit Blauvelt wrote:
> 
>  Upgrading to 5.0, but not upgrading the kernel (I was already running a
>  customized 2.0.30 I was happy with, and have now upgraded to 2.0.33) or
>  Apache (likewise I have a customized version I want to stay with) has
>  resulted in Apache dumping core. And attempts to do a fresh compile of
>  Apache fail (even after installing the kernel-headers rpm - which solved
>  some initial compile problems). It looks like this is a libraries problem.
>  Is there an obvious solution?
> 
>  Although performance is in some respects obviously improved running 5.0
>  instead of 4.2, the upgrade process is still too much of a problem when
>  the system being upgraded isn't purely stock. For one thing, 5.0 insisted
>  on upgrading my sendmail, even though I had specifically unselected it.
>  This wasn't the only package that went ahead and installed unselected.

	You are probably better off with the sendmail update, there was a 
serious security bug in the release that shipped with 4.2.  


Here is what I think:

I don't think you need to install the whoile system again.  I would
almost 
bet that your problem is in some way glibc v2 (libc v6) related.  That
was
why I upgared to 5.0, was for glibc2.  I would recommend finding the
Apache
rpm on the 5.0 CD, and doing an:  'rpm -Uhv apache{whatever}' (this if
course
upgrades apache)  I don't know if there are other reasons for hesitating
on
the install other than if-it-ain't-broke.  But I would venture this may
prevent
difficulty.


Hope this helps.
js
p.s. =)  Good move going to 2.0.33