CentOS 5 :: Force Centos To Search For Software Updates Immediately?
Feb 6, 2011
In general CentOS search automatically after startup for available software updates.Then after some (~20-30) minutes an icon appears in the toolbar which the user can click and install the updates.How can I manually speed up/trigger IMMEDIATELY the search for updates (without waiting for the built-in search)?
There have been no updates recently (for almost two months) on any of my CentOS 5.5 boxes when I run 'yum check-update'. I may be misunderstanding the repo setup, but looking at the file mod dates, it seems that there hasn't been an update since 2011-01-06:[URL]...Meanwhile, a prominent North American Enterprise Linux vendor has had multiple security and bug fixes since then:[URl]...Is CentOS 5.5 still getting updated, or am I missing something (quite possible).
After doing an update a couple of days ago (had previously upgraded to 5.6), the font size in firefox (file forward reload, etc), terminal and the panel (using xfce) are significately smaller. Searching the web, mail lists and the forums have not resulted in finding anyone else with this problem. I did notice that glibc has a bug that is currently being worked on at Redhat but it is unclear if the font problem I am seeing is related. Note also, that the initial upgrade to Centos 5.6 was successful.
I'm using hughesjr' kernel-rt and would like to use ext4 as well. Since the stable release of ext4 is in 2.6.28, I'm wondering if there are any plannedupdates to this kernel-rt release? If not, is it possible to patch this version (2.6.24.7-65.el5rt.centos) of the kernel with stable ext4 patches/tools?
I'm running CentOS 5.4 and noticed that for the past month there haven't been any new updates showing up either on 'yum check-update' or 'yum update' (I'm interested in basic and security updates). Although this may be right, I wonder if there is an online reference where I can check the updates that are released for CentOS (security bulletins) and make sure if there is anything wrong with my update system.
Since updating to C5.7 (64bit) when I go to burn an ISO it is not recognizing the blank disk and I have to use the force option(k3b). In 5.6 it worked fine. This is the same box of disks(and everything else) I was using before the update. The disks seem to burn fine (verify ok). It is just a PITA to have to hit the force button every time.
I run a bunch of CentOS 5.6 servers, where we continuously deploy our software. Our software comes in self-made rpm packages from a network-local yum repository. As bugs happen in software development, I sometimes want to downgrade to the previous release, so force the installation of a specific version of the package.I tried the allow-downgrade plugin, but so far no luck. Neither yum update nor yum install seem to work with allow-downgrade. (It does not seem to do anything?). Does anyone have a working example for yum --allow-downgrade?
This is what I tried: 1) Show current yum version [root]# yum --version
I have CeontOS machines connected to LCD via KVM which causes failure to properly detect screen resolution and I'm stuck with 800x600 until I reset X server with the LCD connected directly to the PC. How can I enforce higher screen resolutions?
EDIT: I followed the advise and left only one resolution in my xorg.conf but it didn't help.
It seems I have some problem with glibc i686 on my VIA CPU. How can I force to install glibc i386.rpm instead of i686 in the clean installation process?
for a x problem I reinstall the complete x packages. I remove some packages with force.Before this yum works perfect. Exact at this time we have problem with our internet connections and yum hangs somewhere when yum load the repositories and or start the update process.Now yum hangs at start from the command. I can start yum some times and no locking error is rise.strace brings:
Have an issue with my CentOS server. I have a fully updated Centos 5.5 server and I have samba set up to serve shares to a couple of groups in my home office. I have it set up to force user/group and force directory create mode 770 and force file mode of 770. This set up works perfectly well for normal connections to the server; no matter who connects, all files and directories are owned by the specified users/group and create modes I specify. The problem is when I try to rsync some files to the same shares. When I do this, rsync ignores the directory/file forced create mode. It will honor the user/group, however. As an example, if I create a directory on one machine connected to the samba share, I get the following:
I am looking for a tool to index the files on my PC to allow full text search. I use recoll on Ubuntu and it does a great job. As I described in a previous post there does not seem to be an rpm package available for recoll on CentOS and I have not been able to build from source.So I tried beagle. In a nutshell the old version of beagle available for CentOS 5.6 does not do a good job of indexing pdf files. The newest version, tried on Linux Mint, does not do much better. And the beagle web site seems to be gone so I am not sure if it is an active product.
I have done some searching and most of what I find appear to be tools for indexing a web server. That is a bit of an overkill for my needs. I simply want to be able to search old email archives, OpenOffice documents, text and pdf files stored and accessed locally on the PC?
I have an application with a complex binary build procedure which links against 30+ application library archives and an array of system library archives. The problem I'm having is the link ordering. Is there a way to tell the g++ linker to keep searching the libraries for unresolved references, regardless of order, instead of rearranging the order the archives are listed on the command line for a one-time-pass? I'm using g++ 3.2.3 on a Linux AS v3update6 machine.
I have an issue with the DHCP clients in a lab environment I am building. The lab is in a dns subdomain but the clients should be able to resolve any machine in the lab subdomain or the parent by using just the hostname. According to everything I have read, the client resolver should do this automagically, trying first the naked hostname, then the FQDN, then walking up the tree of parent domains. But it doesn't.
So I thought I'd just have the dhcp server set the domain search list to include both the local and parent domain. But adding "option domain-search" to dhcpd.conf causes dhcpd to fail on start up. Does the current version of dhcpd in CentOS 5.3 really not support this option?
I noticed that every, say, 5 times I boot CentOS 5.4, a find search is initiated that takes several hours. For example: find . -name rd=rmdir -print I'm not sure if it's related, but, I do have a "alias rd=rmdir" in my .aliases. Would changing it to "alias rd=/bin/rmdir" avoid this problem? I'm using zsh. Is this search necessary?
The problem seems to be a memory issue. Seems the problem only started happening after the last few updates. I have tested the memory with memtest and both servers passed. There hasn't been any new software put on the servers for over 12 months. Server 1 - 3 gig of memory CentOS 5.2 - Linux version 2.6.18-92.1.18.el5 (mockbuild@builder10.centos.org) (gcc version 4.1.2 20071124 (Red Hat 4.1.2-42)) #1 SMP Wed Nov 12 09:19:49 EST 2008 Errors in log
I know this is not as easy or simple as I talk this questions for a free distro. Is it possible, that the last update for the update repository is from 07. Jan. 2011? I know I can get the srpm from rh and compile it by myself.
Is it right --> in case of new releases and limited resources the updates for supportet releases are not highest priority and so we have to wait a little or compile it manually from rh source?
I have been trying all day but so far I am unable to configure yum to use a proxy server to retrieve updates.Due a recent compliance mandate direct internet access had to be removed for a pool of our Cent/RHEL servers. I have added the http_proxy environment variable in /etc/profile using:
I am using the FQDN of the proxy server, and i can ping that FQDN from the CLI without a problem. When I do this and I reboot the server I can get to the internet through the proxy using links/lynx. Yum however stalls out after loading plugins. I have read in a few places that I need a trailing / after the port number above, adding this and rebooting has no effect.
So I tried specifying the yum.conf file... [URL]. When I do this yum still tries to contact the redhat/cent network directly. No behavior change. If I use tcpdump I can see the server I am running yum on try to directly connect without the proxy, which times out for good reason.
The proxy server I am running is squid, but I can see the server I am running yum on blatantly ignore any proxy settings I have tried so far. I am really in a hole on this one as I have to get several updates to fix vulnerabilities found during our last scan.
After making many updates via pup, including FreeNX, my FreeNX installation has broken. It worked flawlessly before the update. Now when I try to connect my client connects, I see the NoMachine splash screen and then I lose the connection with the following details:
Info: Display running with pid '3404' and handler '0x1a037e'.
NXPROXY - Version 3.1.0 Copyright (C) 2001, 2007 NoMachine.[code]......
I have created a yum repository in my local network. Everything seems to be working well except the yum server doesn't remember what was updated, every time I run yum on it the same fies are updated (306 files). And the versions I checked are the same as the files already installed.
Is there a mailing list or an alert where I can subscribe to, so I know if there's critical or moderate patches I have to apply to my Centos 5 servers.
I have my server configured to update automatically every night. However, updates are failing with the following message: There was a problem updating the system. The following error message was reported:
['Not installing key'] If the problem persists, manual intervention may be required. how to troubleshoot or resolve this issue?
I recently installed an image of CentOS 5.4 on my machine.Through copious yum updates and one kernel update, I now find my /etc/issue says that I am at CentOS release 5.6 (Final).However, I need to be at 5.4, which is why I installed it in the first place. How do I first find out which updates are responsible and second revert the responsible updates?