similar to: CentOS 7, yum-cron

Ok, I've just had issues this morning, and went and *looked*. I can see a yum-cron running monthly, sure. Running weekly, I guess. Running daily? Why? And there is *NO* reason whatever for a "yum-hourly*. None. This is CentOS, not ubuntu-snapshot-of-the-moment. I don't know if this is from upstream or not, but it's wrong. I mean, even Redmond only pushes out patches once or

Jon Pruente wrote: > On Fri, May 11, 2018 at 10:36 AM, <m.roth at 5-cent.us> wrote: >> >> And there is *NO* reason whatever for a "yum-hourly*. None. This is >> CentOS, not ubuntu-snapshot-of-the-moment. >> >> I don't know if this is from upstream or not, but it's wrong. I mean, >> even Redmond only pushes out patches once or twice a month,

Hi, Up until now I always kept my servers up-to-date manually. Currently I'm experimenting with yum-cron to automate this process. I read through various online tutorials, and now I have a couple questions. 1. As far as I know, when editing /etc/yum/yum-cron.conf, I can only use the following value for update_cmd : update_cmd = default If I understand this correctly, 'update_cmd =

On Fri, 11 May 2018, m.roth at 5-cent.us wrote: > And there is *NO* reason whatever for a "yum-hourly*. None. This is > CentOS, not ubuntu-snapshot-of-the-moment. Did you have a look at what the hourly run does by default? jh

I receive messages like this from cron often. Not every hour, and not consistently between the servers running CentOS, but at least two per day. Is this normal? /etc/cron.hourly/0yum-hourly.cron: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was 14: HTTP Error 403 - Forbidden Could not retrieve mirrorlist

On Fri, May 11, 2018 at 10:36 AM, <m.roth at 5-cent.us> wrote: > > And there is *NO* reason whatever for a "yum-hourly*. None. This is > CentOS, not ubuntu-snapshot-of-the-moment. > > I don't know if this is from upstream or not, but it's wrong. I mean, even > Redmond only pushes out patches once or twice a month, except for critical > fixes.,,,. > Are

On 6/11/2015 12:16 AM, Harold Toms wrote: > On 10/06/15 17:07, Kirk Bocek wrote: >> I've install yum-cron on a new CentOS 7 host and after a recent >> update I am now getting daily repeating emails about that update >> instead of the single notification I was expecting. Does anyone know >> what's going on? >> >> Kirk >>

I see that there''s a thread from September asking a very similar question ("Official puppetlabs position on cron vs puppet as a service?"). I want to ask what should I take into account when making this decision? Just some background: - All my servers are Red Hat or CentOS - We have about 5 servers managed by Puppet now. The goal is to have ~50 servers. These are generally

Hi, I have a Linux based NAS, which unfortunately appears to be a bit underpowered, heres why I say that: 5 PC's backup to the NAS on a weekly full with hourly incrementals 7 days a week between 7am and 6pm (2 week retention policy). There is no problem with that. Where there is a problem is getting that data off the NAS to the USB attached storage for off site (2 disks swapped weekly). The

On Thu, June 11, 2015 11:14 am, Kirk Bocek wrote: > > > On 6/11/2015 12:16 AM, Harold Toms wrote: >> On 10/06/15 17:07, Kirk Bocek wrote: >>> I've install yum-cron on a new CentOS 7 host and after a recent >>> update I am now getting daily repeating emails about that update >>> instead of the single notification I was expecting. Does anyone know

On 11/15/2017 11:48 AM, m.roth at 5-cent.us wrote: > Mark Haney wrote: >> For the record, this was the only option to handle the task I'm having >> issues with inside cron. >> > Yes. Do not trust your environment, running as a cron job, to be what you > think it is. Try testing it by have your cron job, at the top of the > script, issue the env command. > >

in my prior message, that should be in rkhunter.conf On Wed, Aug 30, 2017 at 11:43 AM, Tony Schreiner <anthony.schreiner at bc.edu> wrote: > This has come up for me on the most recent upgrade, add the line > > HASH_CMD=sha1sum > > On Wed, Aug 30, 2017 at 11:15 AM, <m.roth at 5-cent.us> wrote: > >> Can't remember if I posted this before... We're getting

On 10/06/15 17:07, Kirk Bocek wrote: > I've install yum-cron on a new CentOS 7 host and after a recent update > I am now getting daily repeating emails about that update instead of > the single notification I was expecting. Does anyone know what's going > on? > > Kirk > _______________________________________________ > CentOS mailing list > CentOS at

hey centos long time no hear! :) I'm having a small issue where the backup jobs that I set to run in the crontab of the backup user do not appear to be running. Here's how I set it up (with crontab -e as the backup user): run amanda every night (check at 2:45 and backup at 3) 45 2 * * * /usr/sbin/amcheck /var/log/amanda/crontab/amcheck.log * 3 * * * /usr/sbin/amdump

> On Nov 15, 2017, at 11:48 AM, m.roth at 5-cent.us wrote: > > Mark Haney wrote: >> This might be a bit OT, but I've never had to do this before and what >> I've googled doesn't seem to be working. >> >> I have an ansible playbook that I'm working on that I want to run as a >> cronjob. One task I'm having trouble with is where I have a

Can't remember if I posted this before... We're getting warnings from rkhunterWarning: Checking for prerequisites [ Warning ] All file hash checks will be skipped because: This system uses prelinking, but the hash function command does not look like SHA1 or MD5. Now, googling, I find people saying to rm /etc/prelink.cache, then run rkhunter --propupd. Works. And then,

> > For the record: > # service anacron status > Redirecting to /bin/systemctl status anacron.service > Unit anacron.service could not be found. > You have mail in /var/spool/mail/root It's not a service. As I said, it's run using a script in /etc/cron.hourly > > Sure, anacron is not installed. So how could stuff in /etc/cron.{daily,weekly} > work until June

Hi, I just configured SquidAnalyzer, a nifty little network statistics tool that I'm using mainly in school networks to monitor network usage. I want to run the '/usr/bin/squid-analyzer' script once a day. I took a peek in /etc/cron.daily, and the package already installed an /etc/cron.daily/0squidanalyzer script. I wanted to know at what time CentOS ran the cron.daily scripts,

For some reason I cannot fathom, cron.hourly runs twice each hour on one of my two CentOS-5.4 systems, as reported in /var/log/cron: ------------------------- Mar 16 14:01:01 helen crond[27833]: (root) CMD (run-parts /etc/cron.hourly) Mar 16 14:01:01 helen crond[27834]: (root) CMD (run-parts /etc/cron.hourly) ------------------------- On the other it just runs once, as expected.

Hello Pete, On Mon, 02 Jul 2018 09:59:17 +0100 Pete Biggs <pete at biggs.org.uk> wrote: > > > > So, service is running but what could happen that makes /etc/cron.* not > > being fired? > > You don't say, but if this is CentOS 7, then cron.daily/weekly/monthly > is run using anacron, not cron. Oops, yes CentOS 7, sorry. For the record: # service anacron