Closed (fixed)
Project:
Hosting
Version:
6.x-0.3
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
24 Feb 2010 at 17:02 UTC
Updated:
12 Jun 2014 at 08:59 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
adrian commentedcron can't be run any shorter than once a minute.
that's the lower limit on frequency.
Comment #2
guypaddock commentedIn that case, the option for seconds doesn't make much sense inside the UI...
Comment #3
Anonymous (not verified) commentedYes it does, because when the interval is set to 'every one second', you can run the 'hosting dispatch' command (i.e the entry in your crontab) manually, and it won't return with 'too early for queue' as it normally would. In otherwords it allows you to force the dispatching of the queue, which is useful for development purposes.
So you have to distinguish between the Unix cron interval, and Aegir which maintains its own monitoring of the interval and won't allow a queue to run more than once within a certain amount of time even if cron asks it to.
Marking as won't fix, as this is a feature (in my opinion).
Comment #4
guypaddock commentedIn that case, I'd like to vote for a message to this effect in the user interface?
Comment #5
Anonymous (not verified) commentedHelpful message to that effect committed in HEAD.