Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (hermes.apache.org: domain of apache-users@m.gmane.org
 designates 80.91.229.2 as permitted sender)
To: users@httpd.apache.org
From: Shankar Unni <shankarunni@netscape.net>
Date: Wed, 16 Feb 2005 13:46:52 -0800
Lines: 16
Message-ID: <cv0era$jko$1@sea.gmane.org>
References: <225735BE378BA7489D57D942F109AF69AE622D@va02.va.corp.xtria.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.7.5) Gecko/20041201 Thunderbird/1.0RC1 Mnenhy/0.7
In-Reply-To: <225735BE378BA7489D57D942F109AF69AE622D@va02.va.corp.xtria.com>
Sender: news <news@sea.gmane.org>
Subject: [users@httpd] Re: Apache updates

Warron French wrote:

> If I am running with an Apache-2.0.xxx rpm from RedHat and a new RPM 
> comes out, can I simply do an rpm -i of the new rpm that has been 
> released, or do I have to back up lots of directories and files and etc...?

By default, when you "rpm -U" a package, if any of the original files 
has been modified from its shipped state, it'll be saved as filename + 
".rpmsave" before the new file is put in its place.  I've also sometimes 
seen the case where the original modified file is left in place, and the 
new file is called filename + ".rpmnew", but I don't know under what 
circumstances.

In your case, you just have to preserve the contents of the "conf" 
directory somewhere, *just in case*. Then upgrade, and see what you find 
there.


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org