Description of problem: I often have a minor problem when starting yum: yum reports an existing lock /var/run/yum.pid. Version-Release number of selected component (if applicable): yum-3.2.14-10.fc9.noarch How reproducible: Sometimes Steps to Reproduce: 1.yum -y update 2. 3. Actual results: Loaded plugins: fastestmirror, refresh-packagekit Existing lock /var/run/yum.pid: another copy is running as pid 2898. Another app is currently holding the yum lock; waiting for it to exit... Another app is currently holding the yum lock; waiting for it to exit... Another app is currently holding the yum lock; waiting for it to exit... Expected results: no error report. Additional info: I'm sure a previous yum run had been finished properly! After erasing /var/run/yum.pid, yum runs.
It is probably packagekit running in the background updating the metadata. When you look at the /var/run/yum.pid file do you see if there is a program running that matches the pid in it?
Immediately after reboot (no yum was running before reboot): ps -edalf|grep yum 4 R root 2847 2745 3 80 0 - 6453 - 09:14 ? 00:00:00 /usr/bin/python /usr/share/PackageKit/helpers/yum/get-updates.py none 0 S backes 2850 2834 0 80 0 - 512 pipe_w 09:15 pts/0 00:00:00 grep yum But there is no process running with pid=2847 (I waited some minutes after the ps command), but the file still contains the line "2847"
Umm, the first number after the user running the process is the pid. So: /usr/bin/python /usr/share/PackageKit/helpers/yum/get-updates.py none is the process locking yum