I was going to recommend doing an "rpm -V libapr" command before you did the re-install. It would have given you an idea of what file(s) had been changed since the original install. That might have given you an opportunity to figure out when the corruption happened, and perhaps who was on the system at that time.
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of James Melin Sent: Wednesday, November 15, 2006 10:10 AM To: [email protected] Subject: Re: Strangeness with Apache2 Re-installing the libapr at the same level seems to have solved the problem, though I am at a loss to figure out what could have damaged it in the first place. Now the person who actually owns the apache2 instance is going to put things back the way they configured it in the first place and see if everything works. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
