Bugzilla – Bug 136536
rpmconfigcheck should be run with SuSEconfig, not at boot
Last modified: 2017-04-25 12:55:12 UTC
The /etc/init.d/rpmconfigcheck script is in a wrong location IMHO because - it's useless if no package has been installed since the last boot (which is often the case on home systems that don't run 24/7) - on the other hand, the script is nearly never run on 24/7 servers so you will miss *.rpm* files - nobody reads it because it is hidden behind the nice boot splash - it slows down booting a bit I would highly recommend to remove rpmconfigcheck from the boot process and include it into SuSEconfig - even if not every run of SuSEconfig means rpm run before, it would be a much better place - both on 24/7 and home systems. Plus you could be sure that you are notified instantly. If you want to make it really perfect, run it only if the rpm database is newer than the rpmconfigcheck cache file.
You mean it should *also* run after SuSEconfig. Note that rpmconfigcheck also writes to /var/log/update-messages, so that the user sees it in the KDE panel. Also note that it is only slow the first time it is run after the update, the next times it is really fast. The real problem is that it is much too slow since we switched to rpm-4. The speed was acceptable with rpm-3, currently it is not usable.
(In reply to comment #1) > Note that rpmconfigcheck also writes to /var/log/update-messages, so that > the user sees it in the KDE panel. One more reason for "I want SuSEwatcher back (instead of zen-updater)"? ;-) Maybe you should make rpmconfigcheck sending mails to root instead...
I see that the init script /etc/init.d/rpmconfigcheck still exists on my 11.4 install, but it not set to run by default. Is this script in use anymore / needed? - From what I see in yast sw_single it handles missing files after updates. Setting needinfo to assigne -> can we close this bitrotten bug :-) ?
Yes, it's an optional script. Admins can turn it on if they want the functionality. I don't think it makes sense to drop something just because it is optional.
Michael, I fully agree that the script is useful and should be kept. However the question remains if it should be an initscript. IMHO it would fit better in SuSEconfig, zypper or something like that - in short: at a place that is related to package installation. (The sitiation on 11.4 is still the same as on 10.1 regarding to this script - therefore I'm updating the product ;-)
- SYSEconfig is obsolete - some people install rpms directly without using zypper - it takes no time at boot if the rpm database has not been changed I don't think running it *also* at boot is a bad thing.
AFAIK fixed since some time. closing.