Bug 110379 - Stale lock files continually recreated on login
Stale lock files continually recreated on login
Product: Fedora
Classification: Fedora
Component: rpm (Show other bugs)
athlon Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Johnson
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2003-11-18 17:21 EST by Bruce Riley
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-11-19 09:32:18 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Bruce Riley 2003-11-18 17:21:27 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)

Description of problem:
Stale lock files are created in the rpm directory.  I have removed 
them and rebuilt the database,  but if I log out and log back in 
again,  the __db.003 file is recreated straight away.  If I reboot 
and log in all __db.001 through to __db.003 files are recreated.  
This happens even though I do not run rpm after login,  or attempt to 
install any  packages.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Remove all __db* files from rpm directory
2.rpm -vv --rebuilddb
4. login 

Actual Results:  __db.003 file created in rpm directory.
rpm hangs on attempting to install a package.

Expected Results:  No lock files created

Additional info:
Comment 1 Jeff Johnson 2003-11-19 09:32:18 EST
The __db* files contain locks, but are not the locks themselves.

Yes, the files should be persistent after being created by 1st
rpm command run as root.

You can see the locks by doing
    cd /var/lib/rpm
    /usr/lib/rpm/rpmdb_stat -CA
There should be no locks when rpm is not running.

If login is creating stale locks, then you are running
rpm in your bashrc scripts somehow.

Note You need to log in before you can comment on or make changes to this bug.