Hi Jim,
> just updated and see these *rpm.new files for some config files and
> others. I googled it to see what action I should take
Generally speaking in regards to *.rpmnew and *.rpmsave files:
Do nothing.
You only need to take actions if a service doesn't work anymore. In that case
you should look at the config files of that services and check if the
respective *.rpmnew or *.rpmsave are present. Then check for differences and
possibly and revert back to the old version of that config file. But
generally that should NOT be necessary.
Here is an example:
A new Apache RPM comes aboard. That RPM also has an /etc/httpd/conf/httpd.conf
(among other config files, of course). If that RPM would blindly overwrite
your present httpd.conf, then none of your sites would work anymore. Which
would be bad, right?
So the updated Apache config file sees that you already have a modified
httpd.conf from a previous install there. Hence the httpd.conf provided in
the new RPM is saved as httpd.conf.rpmnew and your own httpd.conf is not
touched at all.
Here is another example: Dovecot. Lets say a new version of Dovecot comes out
and the config file from the old Dovecot which you have is no longer
compatible with the new version of Dovecot as installed through YUM. Now the
RPM also has provisions in for that case:
It saves your old dovecot.conf as dovecot.conf.rpmsave and installs the new
dovecot.conf in /etc/dovecot.conf.
So these "warnings" that you see in YUM aren't bad things that require you to
take action. They're just there that you can take notice about what's
happening.
--
With best regards,
Michael Stauber