From Scire Wiki
<mdisney> my biggest concern with scheduling stuff is the run interval granularity on the clients
right now all the logic for executing stuff is on the client side. i want to be sure that we address situations such as a job that is scheduled to run every minute but the client only runs every 5 or 15 minutes, for example.
if the client runs in daemon mode, no problem
(well, less of a problem)
if the scire client runs from a crontab itself, then it introduces a problem
<codeman> ok so you're talking about the condition where when a job finishes it looks at the next scheduled time to run and that time has already passed, what to do then?
