Bug 134946 - yum leave rpmdb locks when terminated with CTL-c
Summary: yum leave rpmdb locks when terminated with CTL-c
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: rawhide
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-10-07 14:03 UTC by Tom London
Modified: 2014-01-21 22:50 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2005-01-22 19:31:44 UTC


Attachments (Terms of Use)
console output of 'yum update, terminated with CTL-c, status of rpmdb locks' (18.72 KB, text/plain)
2004-10-07 14:04 UTC, Tom London
no flags Details

Description Tom London 2004-10-07 14:03:09 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041002
Firefox/0.10.1

Description of problem:
Running off of Rawhide: 

Terminating yum with a console 'CTL-c',
yum does not clean up rpmdb locks.

Attached shows running yum, killing it
with a CTL-c, and then running
'/usr/lib/rpm/rpmdb_stat -CA' that
shows residual locks.


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

How reproducible:
Always

Steps to Reproduce:
1. yum update
2. kill with CTL-c
3.
    

Actual Results:  residual rpmdb locks

Expected Results:  no locks...

Additional info:

Comment 1 Tom London 2004-10-07 14:04:01 UTC
Created attachment 104892 [details]
console output of 'yum update, terminated with CTL-c, status of rpmdb locks'

Comment 2 Seth Vidal 2004-10-08 14:42:29 UTC
I'm not sure what else I can do. If the process terminates irregularly
then the locks will be out there. I'll look atexit() to see if that
can let me close out the locks but at some level, a process
terminating irregularly is going to leave some things unfinished.


Comment 3 Tom London 2005-01-22 19:23:08 UTC
Seth, I'm not seeing this anymore.

Shall I close this out?

tom


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