On Wed, 2014-01-22 at 11:34 -0500, Zdenek Pavlas wrote:
> > +%files cron-daily
> > +%defattr(-,root,root)
> > +%{_sysconfdir}/cron.daily/0yum-daily.cron
> > +%config(noreplace) %{_sysconfdir}/yum/yum-cron.conf
> > +
> > +%files cron-hourly
> > +%defattr(-,root,root)
> > +%{_sysconfdir}/cron.hourly/0yum-hourly.cron
> > +%config(noreplace) %{_sysconfdir}/yum/yum-cron-hourly.conf
> > +
> > +%files cron-security
> > +%defattr(-,root,root)
> > +%{_sysconfdir}/cron.hourly/0yum-security.cron
> > +%config(noreplace) %{_sysconfdir}/yum/yum-cron-security.conf
> > +
>
> I like this..
>
> > +# NOTE this runs after yum-cron-daily, if that is installed,
> > +# so we will have already waited for that (default 2 hours, 120 mins).
> > +# Also security updates should be smaller than all updates, anyway.
> > +random_sleep = 60
>
> > -# 6*60 = 360
> > -random_sleep = 360
> > +# NOTE that we hold up all the other things in cron.daily as we wait,
> > +# so while waiting for 6+ hours is fine for us it might not be nice
> > +# for logrotate (so wait for 2 hours by default).
> > +random_sleep = 120
>
> Not sure if this is accurate.. cron-daily and cron-hourly run AFAIK
> independently. And yum.pid is definitely locked after the sleep period,
> so we don't hold up other jobs..
Yeh, -security is going in daily too atm. ... I'd played with it a few
ways, including having a cron.d file and cron.hourly and forgot to
change the specfile above to be daily. Daily is easiest, but this is a
downside.
_______________________________________________
Yum-devel mailing list
Yum-devel@lists.baseurl.org
http://lists.baseurl.org/mailman/listinfo/yum-devel
