Hi,
I believe CellServDB should stay the way it is, which is %config.
Why?
What usually happens with this file is that some change is needed 
because a site was changed.  The local admin changed their CellServDV 
and fix it.  EVentually it get's into the main CellServDB and into the 
rpm.  The rpm comes along and fixes the change that was previous made.

Now imagine if this is (noreplace).  The rpm would come along, and not 
change anything.  Then next year, when other changes are made, it 
continues to not change anything.  Eventually, that customized 
CellServDV is so out of date, it's not very good.

That is why it is not (noconfig)

Troy

On 05/28/2009 04:47 AM, Jan Schulze wrote:
> Hi all,
>
> it seems, that the package openafs-client / i386 / 1.4.7-68.2.SL5 replaces an existing CellServDB.
>
> As I understand, configuration files in rpm packages may be declared as %config or %config(noreplace).
> In case of %config, an existing file is renamed to *.rpmsave and the new file from the package is used. This is what I experience with that package.
> In case of %config(noreplace), an existing file is left untouched and the new file from the package is copied to *.rpmnew. This is what I would like to have.
>
> Is there any way to configure the latter behaviour locally (i.e. to override the settings from the package) or can this only be changed in the package itself? What would be the reason to define CellServDB as %config instead of %config(noreplace)?
>
>
> Best Regards
>   Jan Schulze