The same thing happened to me on a system running SuSE 9.0. My
APACHE_MODULES reverted to a default (I think) after a YOU... Restarted
apache2 somewhere down the line, and voila, no more php! I didn't really
know what I was doing, so I had dismissed it as user error, but it would
make me feel less dumb if I could blame it on the YOUpdate.
The PHP installation I am using is self-compiled, not a SuSE package. Could
that be a contributing factor?
James
----- Original Message -----
From: "Hubertus A. Haniel"
On Thu, 20 Oct 2005, David Bear wrote:
Date: Thu, 20 Oct 2005 13:19:32 -0700 From: David Bear
To: suse@karsites.net Cc: suse-security@suse.com Subject: Re: [suse-security] Apache2 update On Thu, Oct 20, 2005 at 08:01:27AM +0100, suse@karsites.net wrote:
Hi there. I have just done an update with YOU.
I'm still having a problem with the apache2 update overwriting my /etc/sysconfig/apache2 configuration file.
I just did 2 machines using yast2 and had no problems with having my config file clobbered.
Just checked mine and got a bit worried as the date has changed - restored the oldest backup I could find and did a diff on it to find out that nothing actually had changed inside the file - which version of SuSE are you running?
Regards Hubba
-- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here