Subject: | |
From: | |
Reply To: | |
Date: | Tue, 12 Apr 2005 14:45:59 +0100 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
On Tue, Apr 12, 2005 at 02:13:58PM +0100 or thereabouts, Mark Nelson wrote:
> Hello
>
> I've just upgraded a number of our servers from SL 3.0.3 to SL 3.0.4,
> this was accomplished without any problems. However the updated rpm for
> named renamed /etc/named.conf to /etc/named.conf.rpmsave, thus disabling
> DNS services for the domain. However the updated openssh rpm created
> it's new config file (/etc/ssh/sshd_config) as
> /etc/ssh/sshd_config.rpmnew. We have two packages behaving differently
> when applying the latest updates.
>
> Wouldn't it be better to have one behaviour or the other, my personal
> one is for .rpmnew config files as this cuts down on the configuration
> files having to be touched manually by the upgrade process.
Hi Mark,
This depends on the individual .spec file.
If it has
%config(noreplace) /etc/ssh/sshd_config
or
%config /etc/named.conf
gives the different behaviours you have observed.
It is up to the packager to decide which one should happen.
There is a very good summary of the different cases here:
http://www-uxsup.csx.cam.ac.uk/~jw35/docs/rpm_config.html
Steve
>
> I understand that sometimes configuration files change and have to be
> replaced due to compatability issues and that we want to follow Redhat's
> lead in most cases.
>
>
> Mark.
>
>
>
>
> -------------------------------------------------------------
> Mark Nelson - [log in to unmask]
>
> IPPP, Department of Physics, University of Durham,
> Science Laborartories, South Road, Durham, DH1 3LE
> Office: +44 (0)191 334 3811, Direct Dial: +44 (0)191 334 3653
>
> This mail is for the addressee only
--
Steve Traylen
[log in to unmask]
http://www.gridpp.ac.uk/
|
|
|