FedoraThis forum is for the discussion of the Fedora Project.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I know this thread is kinda old but I have had this problem for the past 2 days and being a total linux n00b it has been frustrating the hell outta me. No matter what I did I could not get yum to unlock. Finally I just deleted the yum.pid file and it solved my problem. Just thought I would post my experience.
Click here to see the post LQ members have rated as the most helpful post in this thread.
I just figure I would use the search to find something that solved my issue rather than create another thread for a question I am sure has been documented numerous times. Many of the forums I frequent encourage searching, the age of the thread normally does not have a bearing on the resolution. Old or not this thread helped me fix my problem.
I was reading through all the thread and everyone was showing how to see the process, but when I got to this very last post and tried it, it worked like a charm.
Thanks for helping us newbies,.
Originally Posted by axmukher
Open a terminal.
Become superuser by entering 'su' and then the password.
# cd /var/run/
Look for the 'yum.pid' file.
# rm -f yum.pid
Confirm that the 'yum.pid' file has been deleted.
# yum update
This should re-start your update process.
yup, that is what I have had to do a few times, the yum.pid gets eternally locked. Not sure why, but haven't had it happen lately so maybe a fix came down in one of the bazillion updates I see daily lol.
well done guys :
just as a suggestion if you have a tick error.
1. login as root to the linux box
now go true to the terminal.
e.g ) #yum install update
Loaded plugins: langpacks, refresh-packagekit
Existing lock /var/run/yum.pid: another copy is running as pid 1232.
Another app is currently holding the yum lock; waiting for it to exit...
The other application is: PackageKit
Memory : 28 M RSS (356 MB VSZ)
Started: Sun Sep 28 10:30:23 2014 - 00:18 ago
State : Sleeping, pid: 1232
OK ! the PID has been notified at the end of the second line ((1232))