Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am having a problem with my yum process. I have lost my GUI on rebooting. but that is not the question here.
I reboot only to the command line and get something like:
sh-4.1#
The is no GUI. Now when I run something like a yum update command I get the following:
Another app is currently holding the yum lock; waiting for it to exit ...
The other application is: yum
Memory: 19 M RSS (220 MB VSZ)
Started: Thu Oct 23 15:56:20 2014 - 2:34 ago
State: Running, pid 399
In other words I have a yum lock.
and if I run rpm -qa | grep yum I get the follwing:
root 385 0.0 0.0 6388 660 ? S 12:42 0.00 grep yum
So now i type kill -9 385
and it says bash: kill : 385) - No such process.
Now when I type ps aux | grep yum
I get
root 387 0.0 0.0 6388 660 ? S 12:42 0.00 grep yum
It may have killed process 385 and started 387 or just renamed process 385
to 387. I do not know which.
I want to kill the process since it is hogging my whole computer.
I think that this process have a parent that is preventing me from killing the yum process directly.
If so how do I determine what the yum paraent process is?
It is possible that some program issued the yum lock and then failed (or the system crashed) without deleting the yum lock. If that is the case then the yum lock is still set after reboot even though after the reboot you have run no program which issues a yum lock. You can try to delete the yum lock from the command line and then try running yum again.
First find all of the active locks:
find / -iname "*lock*"
Then look at the list of currently active lock files for a lock in a yum directory.
If you find it then delete that lock file, reboot, and try a yum command again. (The reason that I recommend a reboot is to take care of the possibility that for some weird reason yum is automatically running and issuing a lock after every boot.)
rpm -qa | grep yum
root 385 0.0 0.0 6388 660 ? S 12:42 0.00 grep yum
kill -9 385
and it says bash: kill : 385) - No such process.
This only killed the grep process for the rpm -qa command you entered. rpm -qa query's the rpm database for installed rpms (in this case, the yum rpm), not the instance of yum.
Then, when you did this:
Code:
Now when I type ps aux | grep yum
root 387 0.0 0.0 6388 660 ? S 12:42 0.00 grep yum
All you are seeing, again, is the GREP process. the YUM process does not appear to be running. In that case, you should look in /var/run for a file called yum.pid. If it exists, delete it, and you should be good to go.
Changing filesystem from read only to read / write
Oaky, I think that I see the problem now. My Linux filesystem is read only. Therefore it is not possible to get rid of num.pid directly. I will have to first change my Linux filesystem from read only to read write.
I know that the command to do thuis is mount -o remount,rw /dev/hda2/
If my root filesystem is /dev/hda2/
I must use a LiveCD (which I have) to deliver that command. I am not sure what run level that I am in, but I know that it is low and mount is not a command that i can use on my host system.
So in order to do this I must boot from a LiveCD and then chroot over to the system on my hardrive. If I can do this I can change from read to read / write.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.