similar to: Understanding yum automatic upgrades

I'm looking for the Red Hat equivalent of this Debian statement "apt-get ?y install postfix mailscanner spamassassin bind9 clamav ssh webmin webmin-core logwatch libspf2-0 libmail-spf-query-perl" "yum search" can't find some of the packages. Is there some sort of online DB or something that I can search through to see which repository I need to enable for some of

I've read that it's not recommended to automatically apply updates via yum-updated on production servers, but I keep encountering servers that have this enabled. Are any of you doing automatic yum updates on production servers in CentOS 5 via yum-updatesd? Have you experienced any negative side effects? The only thing I can think of is if say a client had a custom version of PHP

Hello, just curious; since March 3rd, 2016 everdays logwatch-mail shows this: Last Status: WARNING: Your ClamAV installation is OUTDATED! WARNING: Local version: 0.99 Recommended version: 0.99.1 on May 4th, 2016 I updated clamav by yum update clamav since then the daily logwatch-mail shows this: Last Status: WARNING: Your ClamAV installation is OUTDATED! WARNING: Local

On one Centos 6.5 server, but not on other C 6.5 servers, Logwatch daily tells me:- Last Status: WARNING: Your ClamAV installation is OUTDATED! WARNING: Local version: 0.98.3 Recommended version: 0.98.4 ---------------- : freshclam -V ClamAV 0.98.4/19275/Sun Aug 10 17:26:35 2014 : clamd -V ClamAV 0.98.4/19275/Sun Aug 10 17:26:35 2014 : rpm -qa clam\* clamd-0.98.4-1.el6.rf.x86_64

Hello gents, First time poster here! Current system running Centos 6.8. Buddy of mine posted a few days back about me wanting to move from Postfix 2.6.x to 2.8 to above, still under centos 6.8. I might move over to 7, but probably not for a while, don't have the resources presently to make this happen. Running Centos 6.8, postfix 2.6.6, clamav 0.99.1. Basic Centos 6.8 box fully patched

I am about to set up a computer with Centos 6 that I'll probably never see again. I don't want to give out the root password, but I would like to have it automatically and transparently update itself. What is the best way to do this? I have been looking at webpages about yum-cron and yum-updatesd but nothing directly addresses Centos 6 and it appears that at least one of those two

ClamAV is installed on my CentOS box. I edited the conf file and assumed all is well. Clearly it isn't. Every day I see in logwatch that my signatures are updated, and the database notified, but if I try to scan a file manually it tells me that my signatures are 55 days old. I tried looking at a how-to, in the hope of identifying the problem, but it is hopelessly out of date, and I

> Date: Saturday, May 14, 2016 16:20:41 -0700 > From: Alice Wonder <alice at domblogger.net> > > On 05/14/2016 01:22 PM, Walter H. wrote: >> Hello, >> >> just curious; >> since March 3rd, 2016 everdays logwatch-mail >> shows this: >> >> Last Status: >> WARNING: Your ClamAV installation is OUTDATED! >> WARNING:

Dear Srs, yum-updatesd-0.9-2.el5 appears that it's not working on freshly installed CentOS 5.2, using: # rpm -qa "yum*" yum-metadata-parser-1.1.2-2.el5 yum-updatesd-0.9-2.el5 yum-3.2.8-9.el5.centos.2.1 yum-fastestmirror-1.1.10-9.el5.centos I see some bugs ([1], [2] and [3]) in the bug tracker, and more info related to other distros like Fedora, etc.. with the same problem.

I recently enabled yum-updatesd on two identical servers and configured it to notify me of updates via e-mail. This worked fine to start with and it notified me on both machines when the kernel-2.6.18-128.1.10.el5.x86_64.rpm update was released last week. However, today I realised that yum-updatesd was not running and thought it was due to rebooting after the kernel update and that I'd

On 03/13/2015 01:06 PM, Blake Hudson wrote: > ken wrote on 3/13/2015 11:36 AM: >> # rpm -q sendmail logwatch >> sendmail-8.13.8-8.1.el5_7 >> logwatch-7.3-10.el5 >> >> One host sends just one email per day, the daily logwatch report. >> Here's /var/log/maillog entries from yesterday (hostnames are changed >> to make designations in this conversation

Running "yum update", yum appears to perform fine and appears to finish but continues to reside in memory: ... Updating : lftp 2/4 Cleanup : lftp 3/4 Cleanup : freetype 4/4 Updated: freetype.i386 0:2.2.1-25.el5_5 lftp.i386 0:3.7.11-4.el5_5.3

Hi All, I am running CentOS5 . Yum pkg was installed by deault fresh installation. pls see below for installed yum pkgs. [root at mailgw ~]# rpm -qa |grep yum yum-updatesd-3.0.5-1.el5.centos.2 yum-3.0.5-1.el5.centos.2 later, I installed below pkg for protection. yum-protectbase-1.0.4-2.el5.centos Now, everything works. But, in this vershion of yum, It has no crontab running. It has a file

Ever since someone told me that one of my servers might have been hacked (not the most recent instance) because I wasn't applying updates as soon as they became available, I've been logging in and running "yum update" religiously once a week until I found out how to set the yum-updatesd service to do the equivalent automatically (once per hour, I think). Since then, I've

My nightly logwatch report had a never before seen section last night, "barracuda spam firewall". I have not problem with the emails it noted as being rejected. But I've always thought of "barracuda" as a commercial product. I have neither configured nor enabled any barracuda software and "yum list '*barrac*'" comes up empty. What is this? Jon -- Jon

Hi, I've just startted configuring yum-updatesd on all our servers to install updates automatically and it works great. But I don't see anywhere in its config or command line options a way to find which package version was replaced by which. Is this achieveable in any way or should I resort to some home-grown scripting again? Thanks. -Amos

Back in the Fedora docs I found on a google, it mentions that in FC6, the preferred tool for updates was the "new" yum-updatesd. Anyone know: a) what theological reason upstream had to drop it altogether, and b) what's the recommended replacement - is it yum-cron? I hand-update some servers, and of course users' workstations, but some system, like home directory servers and

I've been noticing yum updates on several servers I manage over the last few weeks, which I know I didn't perform and could not explain until this morning. At first I suspect a break-in, but found no other evidence or reason an intruder would run the yum updates I was viewing. Yum updates are logged in /var/log/yum.log, which is what Logwatch scans. Seems that the format of the log

yum check-update: clamav.i386 0.88.1-1.el4.kb kbs-CentOS-Extra clamav-data.i386 0.88.1-1.el4.kb kbs-CentOS-Extra clamav-lib.i386 0.88.1-1.el4.kb kbs-CentOS-Extra clamav-update.i386 0.88.1-1.el4.kb kbs-CentOS-Extra yum update: Installing: clamav-db i386 0.88.2-1.el4.rf rpmforge 4.0 M replacing

Hi. I posted this on the clamav list as well, as I do not know whether this is a rpm issue or clamav issue. Strange problem indeed: [root /tmp] #>yum list installed "clamav*" Loaded plugins: fastestmirror Installed Packages clamav.x86_64 0.98-2.el5.rf installed clamav-db.x86_64 0.98-2.el5.rf installed