Bugzilla – Bug 159240
zmd: Be more patient when installing packages manually (rpm -U ...)
Last modified: 2006-06-15 20:21:45 UTC
I installed a package manually and while running the post-inst script, ZMD interfered (3 packages, 3 times; rpm: "waiting to reestablish exclusive database lock"): rpm -Uvh kernel-* tpctl-kmp-default-4.17_2.6.16_rc6_git1_2-18.i586.rpm Preparing... ########################################### [100%] 1:kernel-default ########################################### [ 33%] Setting up /lib/modules/2.6.16-rc6-git1-2-default Root device: /dev/hda7 (mounted on / as reiserfs) Module list: piix processor thermal fan reiserfs Kernel image: /boot/vmlinuz-2.6.16-rc6-git1-2-default Initrd image: /boot/initrd-2.6.16-rc6-git1-2-default Shared libs: lib/ld-2.4.so lib/libacl.so.1.1.0 lib/libattr.so.1.1.0 lib/libc-2.4.so lib/libdl-2.4.so lib/libhistory.so.5.1 lib/libncurses.so.5.5 lib/libpthread-2.4.so lib/libreadline.so.5.1 lib/librt-2.4.so lib/libuuid.so.1.2 Driver modules: ide-core ide-disk piix processor thermal fan Filesystem modules: reiserfs Including: initramfs fsck.reiserfs Bootsplash: SuSE (1400x1050), SuSE (800x600) 10663 blocks warning: waiting to reestablish exclusive database lock 2:kernel-source ########################################### [ 67%] Changing symlink /usr/src/linux from linux-2.6.16-rc5-git9-3 to linux-2.6.16-rc6-git1-2 Changing symlink /usr/src/linux-obj from linux-2.6.16-rc5-git9-3-obj to linux-2.6.16-rc6-git1-2-obj warning: waiting to reestablish exclusive database lock 3:tpctl-kmp-default ########################################### [100%] warning: waiting to reestablish exclusive database lock
can we stat less often or back-off in some fashion?
Ok, I committed a change to zmd so that it waits 30 seconds after the last time the db was changed before it emits the InstalledPackagesChanged event (which is what triggers the reload). Committed in svn r26201.
*** Bug 157535 has been marked as a duplicate of this bug. ***
Note that this could trigger a race condition (if a package is to be installed with zmd or whatever, inside that 30 seconds interval after one has been installed with rpm). This very much depends on the internal architecture, though.