Size: 853
Comment:
|
Size: 1376
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 2: | Line 2: |
Not all implementations include a `crond(8)` command, but all do include `crontab(1)`. |
|
Line 11: | Line 13: |
There are multiple implementations. [[Linux/ArchLinux|Arch]] offers `cronie` and `fcron` packages but promotes [[Linux/SystemdTimerd|timers]] instead. [[Linux/Fedora|Fedora]] offers `cronie` but promotes [[Linux/SystemdTimerd|timers]] instead. (Unsurprising, as both are Red Hat initiatives.) [[Linux/Debian|Debian]] offers a custom distribution of Vixie `cron`, with plans to phase it out for `cronie`. |
|
Line 15: | Line 25: |
== Busybox Crond == | == Usage == === Busybox Crond === |
Cron
Not all implementations include a crond(8) command, but all do include crontab(1).
Contents
Installation
There are multiple implementations.
Arch offers cronie and fcron packages but promotes timers instead.
Fedora offers cronie but promotes timers instead. (Unsurprising, as both are Red Hat initiatives.)
Debian offers a custom distribution of Vixie cron, with plans to phase it out for cronie.
Usage
Busybox Crond
The !BusyBox implementation of Cron (crond(8)) recommends a layer of indirection through named directories. The default configuration runs these tasks:
# min hour day month weekday command */15 * * * * run-parts /etc/periodic/15min 0 * * * * run-parts /etc/periodic/hourly 0 2 * * * run-parts /etc/periodic/daily 0 3 * * 6 run-parts /etc/periodic/weekly 0 5 1 * * run-parts /etc/periodic/monthly
Any scripts in /etc/periodic/hourly will be run on the hourly mark every hour. This is considered preferable to installing a new cronjob.