On Fri, Mar 23, 2012 at 03:28:18PM -0400, James Antill wrote:
> On Fri, 2012-03-23 at 10:38 -0600, Orion Poplawski wrote:
> > On 03/16/2012 10:58 AM, Orion Poplawski wrote:
> > > With the reorg of yum-cron back in July, the ordering in cron.daily was
> > > changed from 0yum.cron to yum-update. Having yum-cron run earlier was a
> > > change
> > > made for reasons outlined in
> > > https://bugzilla.redhat.com/show_bug.cgi?id=445894, namely to run before
> > > makewhatis, mlocate, prelink, rpm, etc. I still think these are relevant.
> > > Were there corresponding reasons for moving it back?
> > Anyone?
> My guess is that it was an accident ... Matthew?
Yes, I think it's by accident. Somewhat relevant from the git log:
commit 2592de5f05c060b906ee8089b841d0fe40f3ed5d
Author: Matthew Miller <mat...@mattdm.org>
Date: Thu Jul 28 16:56:03 2011 -0400
Previously, the entire yum-cron shell script lived in /etc/cron.daily,
using options set in /etc/sysconfig/yum-cron to further restrict the
days when updates and cleanup are done. This moves the main
functionality to a stand-alone shell script, but the logic for
days-to-run stays in the cron scripts. That keeps everything
compatible and is nice and simple, but also allows one to replace the
cron configuration with, for example, updates which run multiple times
per day.
The current possible actions for yum-cron are update and cleanup;
update has special-case code to handle check-only or download-only;
cleanup just runs the commands in cleanup.yum. It would be easy to add
other such actions.
This happened because locally we run the update every hour, and so its
ordering in the daily rotation didn't really occur to me -- mea culpa.
--
Matthew Miller <mat...@mattdm.org>
Senior Systems Architect -- Instructional & Research Computing Services
Harvard School of Engineering & Applied Sciences
_______________________________________________
Yum-devel mailing list
Yum-devel@lists.baseurl.org
http://lists.baseurl.org/mailman/listinfo/yum-devel
