Index: README.txt =================================================================== RCS file: /cvs/drupal-contrib/contributions/modules/cron_control/README.txt,v retrieving revision 1.3 diff -u -p -r1.3 README.txt --- README.txt 5 Sep 2009 15:18:08 -0000 1.3 +++ README.txt 1 Nov 2010 11:51:54 -0000 @@ -12,39 +12,37 @@ Sponsor: Cocomore AG - http://www.cocomo About ===== -Using Cron Control you'll be able to fine tune drupal's cron -espacially in clustered environments. +Using Cron Control, you'll be able to fine-tune Drupal's cron, with +special features for clustered environments. -Using current version of Cron Control you'll be able to turn -on or off single cron jobs or define on which server they should -run. - -For example transcoding videos should not decrease your site's -performance. Using Cron Control you're able to configure each -server in a clustered environment to do that job dedicated while -others serve your pages. - -Or outsource number crunching cron jobs like transcoding videos -to a cloud which doesn't need to be available all the time. -These cron jobs will run as soon as your number cruncher is -available while your regular webservers keep runing "normal" -cron jobs continuously. +Using the current version of Cron Control, you'll be able to turn on or off +individual cron jobs or define the server on which they should run. + +For example, transcoding videos should not decrease your site's performance. +Using Cron Control, you can configure a server in a clustered environment, +to be dedicated to doing that job, while others continue to serve your pages +without loss of performance. + +You can also outsource resource-hungry cron jobs (like transcoding videos) +to a cloud, which doesn't need to be available all the time. These cron jobs +will run as soon as the cloud server resources are available, while your +regular web servers continue to run "normal" cron jobs. Installation ============ 1. Place whole cron_control folder into your Drupal modules/ - directory. + directory, or better, sites/x/modules directory. 2. Enable the cron_control module by navigating to administer > modules 3. Run cron.php on every server -4. Fine tune your cron settings at +4. Fine-tune your cron settings at administer > settings > cron_control -It's recomended to run cron.php on every server round robin +It's recommended to run cron.php on every server, "round robin", using an offset of a couple of minutes. Index: cron_control.info =================================================================== RCS file: /cvs/drupal-contrib/contributions/modules/cron_control/cron_control.info,v retrieving revision 1.1 diff -u -p -r1.1 cron_control.info --- cron_control.info 5 Sep 2009 11:21:33 -0000 1.1 +++ cron_control.info 1 Nov 2010 11:51:54 -0000 @@ -1,4 +1,4 @@ ; $Id: cron_control.info,v 1.1 2009/09/05 11:21:33 mkalkbrenner Exp $ name = Cron Control -description = Control drupal cron's behaviour, also in a clustered environment +description = Control Drupal cron's behaviour, also in a clustered environment core = 6.x Index: cron_control.install =================================================================== RCS file: /cvs/drupal-contrib/contributions/modules/cron_control/cron_control.install,v retrieving revision 1.5 diff -u -p -r1.5 cron_control.install --- cron_control.install 20 Aug 2010 08:45:29 -0000 1.5 +++ cron_control.install 1 Nov 2010 11:51:54 -0000 @@ -54,7 +54,7 @@ function cron_control_schema() { 'not null' => TRUE, ), 'active' => array( - 'description' => t('Boolean to reflect if job is active on a server'), + 'description' => t('Boolean to indicate if job is active on a server'), 'type' => 'int', 'length' => 1, 'not null' => TRUE, Index: cron_control.module =================================================================== RCS file: /cvs/drupal-contrib/contributions/modules/cron_control/cron_control.module,v retrieving revision 1.13 diff -u -p -r1.13 cron_control.module --- cron_control.module 20 Aug 2010 08:45:29 -0000 1.13 +++ cron_control.module 1 Nov 2010 11:51:54 -0000 @@ -3,10 +3,10 @@ /** * @file - * Using Cron Control you'll be able to fine tune drupal's cron - * espacially in clustered environments. - * Using current version of Cron Control you'll be able to turn on - * or off single cron jobs or define on which server they should run. + * Using Cron Control you'll be able to fine-tune Drupal's cron, + * especially in clustered environments. + * Using the current version of Cron Control, you'll be able to turn on + * or off individual cron jobs or define the server on which they should run. * * @author * Markus Kalkbrenner | Cocomore AG @@ -53,8 +53,8 @@ function cron_control_cron() { return; } - // Now we have to avoid that any cron job runs twice. - // Therfor we have to terminate the execution. + // Now we have to avoid any cron job running twice. + // Therefore, we have to terminate the execution. // But first we have to do the same cleanup that would happen without cron control // Record cron time @@ -76,7 +76,7 @@ function cron_control_cron() { exit(); } elseif (strpos($_SERVER['SCRIPT_FILENAME'], 'drush.php') !== FALSE) { - // cron has been started by drush + // cron has been started by Drush /** * @see drush_core_cron() */ @@ -118,7 +118,7 @@ function cron_control_menu() { $items['admin/settings/cron_control'] = array( 'title' => 'Cron Control', - 'description' => "Trim drupal cron's behaviour, also in a clustered environment", + 'description' => "Fine-tune Drupal cron's behaviour, also in a clustered environment", 'access callback' => 'user_access', 'access arguments' => array('administer cron jobs'), 'file' => 'cron_control_admin.inc', @@ -128,7 +128,7 @@ function cron_control_menu() { $items['admin/settings/cron_control/jobs_by_server_addr'] = array( 'title' => 'By server address', - 'description' => "Trim drupal cron's behaviour, also in a clustered environment", + 'description' => "Fine-tune Drupal cron's behaviour, also in a clustered environment", 'access callback' => 'user_access', 'access arguments' => array('administer cron jobs'), 'file' => 'cron_control_admin.inc', @@ -140,7 +140,7 @@ function cron_control_menu() { $items['admin/settings/cron_control/jobs_by_module'] = array( 'title' => 'By module', - 'description' => "Trim drupal cron's behaviour, also in a clustered environment", + 'description' => "Fine-tune Drupal cron's behaviour, also in a clustered environment", 'access callback' => 'user_access', 'access arguments' => array('administer cron jobs'), 'file' => 'cron_control_admin.inc', @@ -170,7 +170,8 @@ function cron_control_adjust_module_weig * Implementation of hook_requirements(). * * @return - * A keyed array of requirements. Each requirement is itself an array with the following items: + * A keyed array of requirements. Each requirement is, itself, an array + * with the following items: * - 'title': the name of the requirement. * - 'value': the current value (e.g. version, time, level, ...). * - 'description': description of the requirement/status. Index: cron_control_admin.inc =================================================================== RCS file: /cvs/drupal-contrib/contributions/modules/cron_control/cron_control_admin.inc,v retrieving revision 1.6 diff -u -p -r1.6 cron_control_admin.inc --- cron_control_admin.inc 20 Aug 2010 08:45:29 -0000 1.6 +++ cron_control_admin.inc 1 Nov 2010 11:51:54 -0000 @@ -27,7 +27,7 @@ function cron_control_get_jobs($order = $jobs[$job->$order][] = $job; } if (empty($jobs)) { - drupal_set_message(t("Cron Control isn't aware of any cron jobs yet. You need to run drupal's cron on every server. If you're only running one webserver or you're using sticky session you can !action.", + drupal_set_message(t("Cron Control isn't aware of any cron jobs yet. You need to run Drupal's cron on every server. If you're only running one webserver or if you're using sticky session, you can !action.", array('!action' => l(t('click here to run cron on this server (!server_addr)', array('!server_addr' => $_SERVER['SERVER_ADDR'])), 'admin/reports/status/run-cron', array('query' => drupal_get_destination())))), 'error'); } }