I have 2 distros in house: redhat 7.3 and fedora core 2. I run period processes (hourly) which verify certain RPMs are installed (using a combination of yum and rpm -q) and also query whats installed on each box so we can determine which boxes have out of date rpms (again using yum and rpm -q). These applications run fine on my redhat 7.3 boxes. I never have to intervene to rebuild the RPM database or erase the __db* files. On fedora core 2 the story is completely different. I find myself having to do this every couple of days on most fedora core 2 machines. Sometimes its just a --rebuilddb other I have to remove the __db* files and then --rebuilddb. Its getting to the point where it seems rpm is *fragile* on fedora core 2. I assume the issue is related to yum and my rpm -q jobs running concurrently? I am sure though. Does anyone else experience the constant rpmdb corruption issues that I am experiencing? Is there a fix or workaround? Most often when these processes run and do nothing but querying. Why would this type of querying cause corruption? Thanks, Steve _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
