Red Hat Bugzilla – Bug 116604
/var/run/yum.pid stays after interupting yum
Last modified: 2014-01-21 17:49:20 EST
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040122 Debian/1.6-1 Description of problem: Use case: "Hey, let's install vi and vim." Ok type: "yum install vim-minimal vim-enhanced" No, it will ask are you sure thing later, let's just hit CTRL-C and type "yum -y install vim-minimal vim-enhanced". Hmm, what a heck, it doesn't work: Traceback (most recent call last): File "/usr/bin/yum", line 30, in ? yummain.main(sys.argv[1:]) File "/usr/share/yum/yummain.py", line 169, in main lock('/var/run/yum.pid', mypid) File "/usr/share/yum/yummain.py", line 121, in lock while not yumlock.lock(lockfile, mypid, 0644): File "/usr/share/yum/yumlock.py", line 10, in lock if not msg.strerror == "File exists": raise msg OSError: [Errno 17] Tiedosto on olemassa: '/var/run/yum.pid' Ok, need to remove /var/run/yum.pid file. Why doesn't yum remove /var/run/yum.pid file when it dies? Version-Release number of selected component (if applicable): yum-2.0.4.20040103-2 How reproducible: Always Steps to Reproduce: 1. yum something 2. ctrl-c 3. yum again something 4. remove stale /var/run/yum.pid file 5. yum again Actual Results: Losing another valuable 5 seconds of your "life". Expected Results: Perfect user experience. Additional info:
1. your expected results are pretty funny 2. this has been fixed in the latest yum daily release -I'll try to encourage this to show up in rawhide. closing this as fixed, upstream.
Wow! It took only took 5 seconds to close this. ;-) That's perfect user experience.