SCIENTIFIC-LINUX-DEVEL Archives

October 2004

SCIENTIFIC-LINUX-DEVEL@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:
From:
John Franks <[log in to unmask]>
Reply To:
John Franks <[log in to unmask]>
Date:
Tue, 5 Oct 2004 10:20:36 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (18 lines)
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.


--
John Franks <[log in to unmask]>
Dept of Mathematics, Northwestern Univ

ATOM RSS1 RSS2