Needs work
Project:
SuperCron
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
5 Jun 2009 at 15:51 UTC
Updated:
16 May 2010 at 10:21 UTC
Calibrating long cron hook invocations is a challenge; what if, for example, one overloads the task list of the Search hook and it collides with itself on a second cron call ? Having a semaphore protect those instances (and report on hung semaphores if a certain timeout has been reached) would make the multithreading feature more useful.
Comments
Comment #1
vietcoop commentedComment #2
MisterSpeed commentedWe have a partial solution up (we skip hooks in process), but will get something better down the 2.x line by introducing better hook hangs recoverability