[PATCH 2/3] Make yum-{daily, hourly}.cron.sh use independent lockfiles.

Zdenek Pavlas zpavlas at redhat.com
Thu Jan 16 09:29:44 UTC 2014


> >  yum-cron/yum-cron-hourly.service  |  6 +++---
> >  yum-cron/yum-cron-hourly.sysvinit | 10 +++++-----
> >  yum-cron/yum-cron.sysvinit        |  4 ++--
> >  yum-cron/yum-hourly.cron.sh       |  2 +-
> >  4 files changed, 11 insertions(+), 11 deletions(-)
> 
>  I understand the desire here, we don't want them to randomly "kill"
> each other by being running when the other wants to run ... but won't
> that happen anyway due to them mostly holding the yum lock at the same
> time? (big package downloads would be the significant exception here).
> 
>  Might be better to wait for N minutes checking the lock and keep using
> the same lock?

No, yum-cron, yum-cron-hourly, and yum itself should still share the sam
yum.pid lockfile.. The wording is unfortunate.. I ment these lockfiles:

$ grep ^lockfile *.sysvinit
yum-cron-hourly.sysvinit:lockfile=/var/lock/subsys/yum-cron-hourly
yum-cron.sysvinit:lockfile=/var/lock/subsys/yum-cron

$ grep lock yum-cron.service 
ExecStart=/bin/touch /var/lock/subsys/yum-cron
ExecStop=/bin/rm -f /var/lock/subsys/yum-cron

These are used to enable/disable "exec /usr/sbin/yum-cron"
in /etc/cron.daily/0yum-{daily,hourly}.cron scripts.  Currently,
both scripts check /var/lock/subsys/yum-cron.


More information about the Yum-devel mailing list