Some configs are lost after an update.

Support knowledgebase (hmeyer_update_lost_config)
Applies to

SuSE Linux: All versions

Symptom

Some services or programms have lost their configuration after having done an update of the system. They are now running with standard configurations.

Cause

When doing an Update, rpm has to decide for each package, whether the configuration file(s) of the old version are usable for the new version of the package. In extrem case the format/syntax of the config file has changed that much, that the old configuration file is no longer usable. In such a case rpm installs the standard config file of the new package. Your old config file will not be lost, but instead be saved with the file suffix *.rpmsave next to the new config file.

On the other hand, rpm saves the standard config file of the new package with suffix *.rpmnew, if the old configuration is kept.

Solution

After an update you should search for the *.rpmsave files. It might also make sense to check for *.rpmnew files, since these files may contain information about new config options for that package.

After the update is done, let user root update the locate database (this might take a few minutes):

  updatedb

Afterwards you can search for these files.

  locate "*.rpmsave"
  locate "*.rpmnew"

Now you can compare these files with the installed config files and decide what changes have to be done.


Keywords: UPDATE

SDB-hmeyer_update_lost_config, Copyright SuSE Linux AG, Nürnberg, Germany - Version: 05. Jul 2001
SuSE Linux AG - Last generated: 07. Mai 2002 by hmeyer (sdb_gen 1.40.0)