Red Hat Bugzilla – Bug 853497
[BUG] beaker-expire-distros needs locking
Last modified: 2012-10-11 19:50:37 EDT
Description of problem:
beaker-expire-distros needs to verify its not already running before starting.
Version-Release number of selected component (if applicable):
I think this should be the responsibility of whoever is invoking beaker-expire-distros, e.g. the cron job if that's what the site is using.
Doesn't cron already have support for preventing the same job running concurrently?
(In reply to comment #1)
> Doesn't cron already have support for preventing the same job running
It seems not. But we can very easily add some locking to the cron job which we ship.
On Gerrit: http://gerrit.beaker-project.org/1315
Beaker 0.9.4 has been released.