On 11 May 2018 at 11:36, wrote:
> 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
John Hodrien wrote:
> On Fri, 11 May 2018, m.r...@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?
>
Ok, I just did, and I see in the configuration
On Fri, 11 May 2018, m.r...@5-cent.us wrote:
In a work environment? Or production? No way is there going to be an
instant update. In most cases, you need to test whether that update is
going to break things, and that will get you a ton more grief from users
and management.
Even if it's rated
Jon Pruente wrote:
> On Fri, May 11, 2018 at 10:36 AM, 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
On Fri, 11 May 2018, m.r...@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
___
CentOS mailing list
On Fri, May 11, 2018 at 10:36 AM, 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
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
Hi, folks,
Has anyone else seen the issue of having an excludes= in /etc/yum.conf,
but yum-cron appears to be ignoring it?
This may have been the case earlier this year, where it seemed to
partly install a new kernel, then not done the post-install. I *think*
that's what I'm seeing on a
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=x86_64=os=stock
error was
I want to use yum-cron with email notificaton.
The upgrade runs, but i get no message. yum-cron aborted with this
message:
[root@h1 yum]# yum-cron
Traceback (most recent call last):
File "/usr/sbin/yum-cron", line 711, in
main()
File "/usr/sbin/yum-cron", line 708, in main
Hi.
I'm installed yum-cron and set:
# by default MAILTO is unset, so crond mails the output by itself
# example: MAILTO=root
MAILTO=r...@domain.org.ua
I see in log that yum-cron done it's job:
# grep yum /var/log/cron
Aug 11 03:08:02 venti run-parts(/etc/cron.daily)[4516]: starting
0yum.cron
On Mon, Aug 11, 2014 at 7:30 AM, 1...@setevoy.kiev.ua wrote:
Hi.
I'm installed yum-cron and set:
# by default MAILTO is unset, so crond mails the output by itself
# example: MAILTO=root
MAILTO=r...@domain.org.ua
I see in log that yum-cron done it's job:
# grep yum /var/log/cron
Aug
Hi all,
I use yum-cron with my new CentOS 6-installs and rather like it. So much in
fact, that I tried getting it to work in the older CentOS 5-installs I also
have scattered at the department.
Unfortunately it doesn't seem to work for some reason. I found this;
13 matches
Mail list logo