On 2022-09-02 07:36, Simon Becherer wrote:
Am 01.09.22 um 21:42 schrieb Patrick Shanahan:
* Nicolas Kovacs <> [09-01-22 15:11]:
Le 01/09/2022 à 20:37, Bengt Gördén a écrit :
Check if you have unresolved configuration files? run: rpmconfigcheck
Right, here goes:
[root@alphamule:~] # rpmconfigcheck Searching for unresolved configuration files Please check the following files (see /var/adm/rpmconfigcheck): /etc/chrony.conf.rpmnew /etc/fonts/conf.d/30-metric-aliases.conf.rpmsave /etc/localtime.rpmnew /etc/nsswitch.conf.rpmnew /etc/postfix/main.cf.rpmnew /etc/postfix/master.cf.rpmnew /etc/pulse/client.conf.d/50-system.conf.rpmsave /etc/sane.d/dll.conf.rpmsave /etc/sudoers.rpmnew /etc/sysctl.conf.rpmnew /etc/vbox/vbox.cfg.rpmorig /etc/zypp/zypp.conf.rpmnew /var/lib/unbound/root.key.rpmnew
Now what ?
example: meld /etc/chrony.conf.rpmnew /etc/chrony.conf resolve differences wanted (or not) save /etc/chrony.conf, rm /etc/chrony.conf.rpmnew
go to the next
or use tkdiff
or use midnight commander menue command / compare-files (free tranlation from german) here you have two panels (i think in kdiff also) and you are able to chose what you like to have in your new configuration. -> this makes sense if you have edit the files before to your needs, otherwise it could be overwritten by new (unwanted) config. after that delete the .rmpnew and .rpmsave files.
Thing is, meld compares both files and allows you to edit both files simultaneously, accepting or rejecting a change line by line, letter by letter, till you are happy, then save, or not.
i strongly recomend to copy the .conf AND the .rpmnew/save file before to a backup dir, in case you destroy your config.
Yes. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)