Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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'm trying to kill a couple yum processes that started then locked up at the Transaction Check part of the install. One of the processes has been locked since Friday and the other from this afternoon. One was to update ntp, the other to update rsync.
I have attempted to use "kill -9 PID" as well as "pkill -9 PID" but they continue to show with "ps aux | grep yum". This is running on the main server where everyone gets their NFS shares from so I can't just reboot it. Is there any way to kill these processes?
Just checked and there is no yum-updatesd service running or even present on the server. It isn't listed under chkconfig either. The server is currently running FC4(Stentz).
Ok, just so you know FC4 is beyond EOL(End Of Life) and has not had any updates(of any kind) in 3(?) years. The current release of Fedora is F11(7 versions behind). This is going to cause you problems on at least two fronts. First it leaves you vulnerable to attack(no security updates). Second, since virtually no one has run that version in years, there is going to be almost no one around who is going to have current knowledge on FC4. Yum may be hanging becuase the old repos (assuming stock setup) no longer exist.
Since you list Centos in your profile, I would strongly suggest you move this machine to 5.3 as soon as possible. With each version of Fedora only being supported for 13 months and your situation, it really does not make sense to use Fedora. Since Centos has a five year plus support life, you will have updates until 2012(?) and plenty of people around with current experience on C5.3.
It still isn't killing but rsync is finally working for backing up the server so I don't have to worry about this anymore. It will eventually be updated to Centos 5.3, the problem was trying to get rsync going as it was hanging before but seems to be fine now. Thanks for the suggestions.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.