Drupal-7 has 'poor mans cron' style functionality built in, turned on and set to run every 3 hrs by default. There's an obvious potential for collision with hosting-cron runs. See admin/config/system/cron on a d7 site.

So I suggest aegir should hard code drupal-7's cron to 'never' in a similar way to that done for cache in d6.

Comments

Anonymous’s picture

Anonymous (not verified) commented

The problem is not everyone enables the Cron feature in Aegir..

we should set this conditionally if the Cron feature has been enabled, otherwise leave the default behaviour as-is.

steven jones’s picture

steven jones commented

We've stepped away from hardcoding variables recently, so while agree with this, should we actually do this?

anarcat’s picture

anarcat commented

I guess this could be conditionnal - if we have the cron module enabled in the frontend, we should disable d7's builtin cron...

Then people can override it in local.settings.php / global.inc if they need to...

steven jones’s picture

steven jones commented
Status: Active » Closed (won't fix)

We'd have the issue of doing this because say you've enabled the cron queue, provision a bunch of sites and then disable the queue, all those sites would have D7's poormanscron disabled, whereas new ones wouldn't, and it would be a bit weird. Also, most of the time I disable the cron queue and run cron from some other system, like Jenkins, and I still don't want the poormanscron running.

I firmly believe it's better to try not to automate this magically, like we used to do with cache, and just let people configure their own sites where it makes sense for them. Less pain all around.