i recently run
on a centos server and this replaced the current
config files with a new one.
this happened with
but i think it can happen with other packages as well.
please advise how such issues can be prevented from happening again.
The first preventive measure would be you: before updating check what does it want to update and where the update comes from (what repo is using). Do not accept updates at willy-nilly
The second preventive measure would be you: learning how to manage yum.
Keywords like: exclude, enable, disable, protect and priority might assist you in managing packages update.
Before you run yum update, you need to protect yourself by saving a copy of your custom configuration files.
1 Like
I have seen rpm's that rename a conflicting config file to .rpmsave or rename the new file to .rpmnew .
But not every rpm is nice like that.
1 Like
is it possible to do a dry-run to see what
yum update
will do with the config files ?