Cron

From ArchWiki
Revision as of 16:28, 25 January 2010 by Pointone (Talk | contribs) (initial content)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.


Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어


External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

Tango-document-new.pngThis article is a stub.Tango-document-new.png

Notes: please use the first argument of the template to provide more detailed indications. (Discuss in Talk:Cron#)
Summary help replacing me
An overview of the standard task scheduling daemon on GNU/Linux systems.

From Wikipedia:cron:

Cron is a time-based job scheduler for Unix-like computer operating systems. Cron enables users to schedule jobs (commands or shell scripts) to run automatically at a certain time or date. It is commonly used to automate system maintenance or administration, though its general purpose nature means that it can be used for other purposes, such as connecting to the Internet and downloading email.

Installation

There are multiple cron implementations available for users to choose from. Template:Package Official (Dillon's Cron) is available in [core] and is installed as part of the base group.

# pacman -S dcron

Alternatively, users may wish to install Template:Package AUR or Template:Package AUR from the AUR; both offer a wider range of features and configuration options.

Configuration

The cron daemon parses a configuration file known as crontab. Each user on the system can maintain a separate crontab file to schedule commands individually. The root user's crontab is used to schedule system-wide tasks.

crontab files should not be edited directly. Instead, users are encouraged to utilize the Template:Codeline command. Issuing Template:Codeline, for example, opens the current user's crontab in their preferred editor.

By default, root's crontab looks like this:

Template:File

The files themselves are usually stored as Template:Filename. For example, root's crontab is found at Template:Filename.