SCIENTIFIC-LINUX-USERS Archives

July 2017

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV
Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: yum-cron
From:
Nico Kadel-Garcia <[log in to unmask]>
Reply To:
Nico Kadel-Garcia <[log in to unmask]>
Date:
Tue, 25 Jul 2017 08:11:38 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (18 lines) 
On Mon, Jul 24, 2017 at 10:18 PM, Stephen Isard
<[log in to unmask]> wrote:
> On Mon, 24 Jul 2017 20:36:44 -0400, Nico Kadel-Garcia <[log in to unmask]> wrote:
>
>>On Mon, Jul 24, 2017 at 10:59 AM, Stephen Isard
>><[log in to unmask]> wrote:
>>> On Sun, 23 Jul 2017 23:06:27 -0400, Nico Kadel-Garcia <[log in to unmask]> wrote:

>>Frankly, no, I can't deduce that kind of thing remotely and with
>>limited information. yum-cron is normally a shell script: you should
>>be able to run it as the root user, typically with the "bash -x
>>/etc/cron.daily/yum-cron" options, and get a better handle on what
>>precisely it's trying to pull down.
>
> It is now a python script, making lots of python library calls.

Oh, for pete's sake.., why did they do *that* ?

ATOM RSS1 RSS2