Master Linux crontab: Schedule Scripts, Syntax, and Practical Examples

Why use crontab?

When a server needs regular maintenance—such as cleaning old backup files—a shell script can be executed automatically using Linux's crontab command, which schedules tasks at specified times.

Key features of crontab

Runs tasks without user interaction, ideal for background automation.

Supports multiple independent jobs, each with its own schedule.

Allows execution on specific dates and times (e.g., the last day of each month).

Enables recurring intervals such as hourly or daily runs.

Persists across system reboots, automatically restoring scheduled jobs.

Typical use cases

System maintenance – periodic log cleanup, database backups.

Data analysis – scheduled analytics scripts and report generation.

Network tasks – regular connectivity checks, email notifications.

Basic crontab syntax

* * * * * command-to-execute

Fields represent minute hour day-of-month month day-of-week respectively.

Common scheduling examples

Run a script every day at 5 AM: 0 5 * * * /path/to/command/script.sh Run a script on the last day of each month (example shown uses day 1 for illustration): 0 0 1 * * /path/to/command/script.sh Run a script hourly:

0 * * * * /path/to/command/script.sh

Editing the crontab file

Open the editor with crontab -e. The system may prompt you to choose an editor via select-editor. Add, modify, or delete lines following the syntax above. For example, to schedule the 5 AM job: 0 5 * * * /path/to/command/script.sh It is common to redirect output to avoid clutter:

/path/to/command/script.sh > /dev/null 2>&1

Saving and locating crontab files

After saving and exiting the editor, the new job becomes active at the next scheduled time. Crontab files are stored under /var/spool/cron/.

Ensuring script executability

The script must have execute permission; set it with:

chmod +x /path/to/script.sh