SCIENTIFIC-LINUX-DEVEL Archives

October 2004

SCIENTIFIC-LINUX-DEVEL@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

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

Print Reply
Sender:
Maillling list for Scientific Linux developers worldwide <[log in to unmask]>
Date:
Tue, 5 Oct 2004 10:42:34 -0500
MIME-version:
1.0
Reply-To:
Troy Dawson <[log in to unmask]>
Content-type:
text/plain; format=flowed; charset=us-ascii
Subject:
From:
Troy Dawson <[log in to unmask]>
In-Reply-To:
Content-transfer-encoding:
7BIT
Comments:
To: John Franks <[log in to unmask]> cc: [log in to unmask]
Parts/Attachments:
text/plain (28 lines)
John Franks wrote:
> When doing an upgrade from 3.0.2 to 3.0.3 I noticed that my
> /etc/cron.daily/yum.cron is not replaced (which is good), but a
> new version is placed in /etc/cron.daily/yum.cron.rpmnew.  The
> problem is that yum.cron.rpmnew is executable and in cron.daily so
> it will get run by cron (in addition to the local yum.cron).
>
> I believe if it were not executable it would not be run, but I haven't
> tested this and I may be wrong.
>
> Also, my personal preference would be to have the new /etc/yum.conf
> installed as /etc/yum.conf.rpmnew rather than overwriting the local
> yum.conf.  But I understand others may differ.
>
Hi John,
The cron.daily (and cron.hourly and weekly) all have been coded to ignore
*.rpmnew and *.rpmsave.
It does make you nervous when you see this, yes, so I understand your
apprehension.  But don't worry, it's been seen and tested, and both of them
will not be run.  Only the /etc/cron.daily/yum.cron
Troy

--
__________________________________________________
Troy Dawson  [log in to unmask]  (630)840-6468
Fermilab  ComputingDivision/CSS  CSI Group
__________________________________________________

ATOM RSS1 RSS2