![](https://seccdn.libravatar.org/avatar/182fb33ea8f9cc7e36f4e343fb97faeb.jpg?s=120&d=mm&r=g)
* Erik Jakobsen <eja@urbakken.dk> [Sep 09. 2003 07:12]:
When I boot, I receive this message:
Please check the following files (see /var/adm/rpmconfigcheck):
/etc/crontab.rpmsave /etc/cups/classes.conf.rpmsave /etc/cups/printers.conf.rpmsave /etc/mail/spamassassin/local.cf.rpmnew /etc/mail/spamassassin/local.cf.rpmnew /etc/mailman.mail-gid.rpmnew /etc/opt/kde3/share/config/k3b/k3bsetup.rpmsave /etc/sane.d/dll.conf.rpmsave /usr/lib/cups/backend/smb.rpmsave /usr/lib/mailman/Mailman/mm_cfg.py.rpmsave /usr/lib/mailman/Mailman/mm_cfg.pyc.rpmsave
<notice>'/etc/init.d/rc3.d/S13rpmconfigcheck start' exits with status 0
I the mentioned directory, I can see that there are md5sums to be found.
If running md5 on the mentioned files, and this test say ok, not ok. What to do in both conditions ?
It's just that when you installed an rpm with a config file, and the config file was changed on the system from last install, two things can happen. Rpm either makes a backup of the one there to .rpmsave, or saves the one it provides in .rpmnew. So you should check the configfiles for options you might need, and if you made sure of that, delete the file. It's just a check for the sysadmin to be aware of possible changes in configfiles. -- Mads Martin Joergensen, http://mmj.dk "Why make things difficult, when it is possible to make them cryptic and totally illogical, with just a little bit more effort?" -- A. P. J.