summaryrefslogtreecommitdiff
path: root/modules/system/system.module
diff options
context:
space:
mode:
authorDries Buytaert <dries@buytaert.net>2002-12-29 21:46:13 +0000
committerDries Buytaert <dries@buytaert.net>2002-12-29 21:46:13 +0000
commitf281f0a7e32c0fcfd51fc07a76203427e1c6c25b (patch)
tree3da57eec459761b2d3f41b1e2f585f9e6178a8c0 /modules/system/system.module
parent62fa5541dd2d865620a958722781f345af5f69f6 (diff)
downloadbrdo-f281f0a7e32c0fcfd51fc07a76203427e1c6c25b.tar.gz
brdo-f281f0a7e32c0fcfd51fc07a76203427e1c6c25b.tar.bz2
- Fixed a typo in the documentation, as well as extended the documentation
while I was at it.
Diffstat (limited to 'modules/system/system.module')
-rw-r--r--modules/system/system.module2
1 files changed, 1 insertions, 1 deletions
diff --git a/modules/system/system.module b/modules/system/system.module
index 19678c1a8..112b05a57 100644
--- a/modules/system/system.module
+++ b/modules/system/system.module
@@ -24,7 +24,7 @@ function system_help_cron() {
$output .= "<p>Whenever <a href=\"". path_uri() ."cron.php\">". path_uri() ."cron.php</a> is accessed, cron will run: it checks for the jobs cron controls, and their periods in seconds. If a certain task wasn't executed in the last n seconds, where n is the period of that job, it will be executed. When all the executed commands terminate, cron is done.</p>";
$output .= "<p>The recommended way to setup your cron system is to setup a Unix/Linux crontab that frequently visits <a href=\"". path_uri() ."cron.php\">". path_uri() ."cron.php</a>. Note that cron does not guarantee the commands will be executed at the specified interval. However, Drupal will try his best and run the crons as close to the specified intervals as possible. The more you visit cron.php, the more accurate cron will be.</p>";
$output .= "<p>If your hosting company does not allow you to setup crontabs, you can always ask someone else to setup a crontab for you. After all, virtually any Unix/Linux machine with access to the internet can setup a crontab to frequently visit <a href=\"". path_uri() ."cron.php\">". path_uri() ."cron.php</a>.</p>";
- $output .= "<p>For the Unix/Linux crontab itself, use a browser like <i>lynx</i> or <i>wget</i> but make sure the process terminates: either use <code>/usr/bin/lynx -source <?php echo path_uri(); ?>cron.php</code> or <code>/usr/bin/wget -O /dev/null <?php echo path_uri(); ?>cron.php</code>. Take a look at the example scripts in the <code>scripts</code>-directory and make sure to adjust them to your needs. A good crontab-line to run the cron-script once every hour would be: <pre> 00 * * * * /home/www/drupal/scripts/cron-lynx</pre></p>";
+ $output .= "<p>For the Unix/Linux crontab itself, use a browser like <i>lynx</i> or <i>wget</i> but make sure the process terminates: either use <code>/usr/bin/lynx -source <?php echo path_uri(); ?>cron.php</code> or <code>/usr/bin/wget -O /dev/null <?php echo path_uri(); ?>cron.php</code>. Take a look at the example scripts in the <code>scripts</code>-directory and make sure to adjust them to your needs. A good crontab-line to run the cron-script once every hour would be: <pre> 00 * * * * /home/www/drupal/scripts/cron-lynx.sh</pre>Note that it is essential to access <code>cron.php</code> using a browser; don't run it using command line PHP and avoid using <code>localhost</code> or <code>127.0.0.1</code>, or some features won't work as expected. For all the environment variables to be correct; use a browser to access <code>cron.php</code> on a publicly accessible domain.</p>";
return $output;
}