On Wed, 2014-01-15 at 10:34 +0100, Zdenek Pavlas wrote: > --- > 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? _______________________________________________ Yum-devel mailing list Yum-devel@lists.baseurl.org http://lists.baseurl.org/mailman/listinfo/yum-devel
