Clean up config-defaults.php: remove $cfg->maxrunage

$cfg->maxrunage is no longer needed (has been removed in
03203d96

)
Signed-off-by: Ruslan Kabalin <ruslan.kabalin@luns.net.uk>

htdocs/lib/config-defaults.php

@@ -212,21 +212,6 @@ $cfg->accessidletimeout = 600;
 // Whether to show the onlineusers sideblock
 //$cfg->showonlineuserssideblock = true;
 
-// CRON job maximum run age in SECONDS
-// ... Mahara decides to run a cron job only if the "next run time" is between the current date+time and (max run age) seconds ago.
-//
-// IMPORTANT:  THIS MUST BE EQUAL TO OR GREATER THAN YOUR CRON JOB THAT HITS {$cfg->wwwroot}/lib/cron.php
-// ... The setup/install instructions require you to set a server cron job to hit the cron.php.
-// ... The default assumption by Mahara is that this will be every minute.
-// ... Not all hosting providers will allow you to schedule a cron job every minute.  Also, you may for your own purposes
-//     not want to have a cron job every minute for CPU / performance reasons.
-//
-// If this is not set properly, any cron periodicities less than your server cron periodicity will likely be perpetually skipped.
-// This will be evident in cron job report that is output by your server after hitting cron.php.
-//
-// EXAMPLE:  Your cron job hits cron.php every 15 minutes.  Then $cfg->maxrunage must be 900 or greater.
-$cfg->maxrunage = 300;
-
 // if importing Leap2A over an xmlrpc mnet connection, set this to something higher than 0 to log import information
 // see the constants in import/leap/lib.php
 $cfg->leapovermnetloglevel = 0;