From 7ab2b40d743fcccecb7e7ec1d20850ca7c0bd50c Mon Sep 17 00:00:00 2001 From: Dries Buytaert Date: Thu, 7 Feb 2002 19:59:37 +0000 Subject: - Included the cache documentation. --- modules/system/system.module | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) (limited to 'modules/system') diff --git a/modules/system/system.module b/modules/system/system.module index f84c204f8..5dc167c4c 100644 --- a/modules/system/system.module +++ b/modules/system/system.module @@ -2,8 +2,22 @@ // $Id$ function system_help() { + $output .= "

Drupal comes with system-wide defaults but the setting-module provides control over many Drupal preferences, behaviors including visual and operational settings.

"; + $output .= system_help_cache(); + $output .= system_help_cron(); + return $output; +} + +function system_help_cache() { + ?> +

Cache

+

Drupal has a caching mechanism that stores dynamically generated pages in a database. By caching a page, Drupal does not have to generate the page each time it is requested. Only pages requested by anonymous users are being cached. When a cached page is accessed, Drupal will retrieve that page with minimal overhead using one SQL query only, thus reducing both the server load and the response time.

+

Drupal's caching mechanism can be enabled and disabled by the site administrators from the 'settings' page. He can also define how long cached pages should be kept.

+ -

Drupal comes with system-wide defaults but the setting-module provides control over many Drupal preferences, behaviors including visual and operational settings.

Cron

Some settings require a cron or crontab. Cron (which stands for chronograph) is a periodic command scheduler: it executes commands at intervals specified in seconds. It can be used to control the execution of daily, weekly and monthly jobs (or anything with a period of n seconds). Automating tasks is one of the best ways to keep a system running smoothly, and if most of your administration does not require your direct involvement, cron is an ideal solution.

Whenever cron.php 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.

-- cgit v1.2.3