Getting Started with Cron on macOS and Linux: Setup, Commands, and Common Pitfalls

Cron is a daemon that runs scheduled commands at regular intervals on Unix-like systems, including macOS and Linux. It checks its configuration files every minute and can email the output of each job to the task owner.

To verify that cron is running, you can execute sudo launchctl list | grep cron. The primary tool for managing cron jobs is crontab, which provides several sub‑commands: crontab -e – edit the current user's crontab file (or specify a user to edit another’s). crontab -l – list the current crontab entries. crontab -r – remove the current crontab file.

A typical cron entry follows the format */10 * * * * command, meaning the command runs every 10 minutes. After saving a new entry, you will see a message like “installing new crontab”, indicating success.

Common issues include missing environment variables because cron runs with a minimal environment (usually /usr/bin/sh). Ensure scripts use absolute paths or explicitly set needed variables; otherwise, commands like Python or adb may not be found.

Restarting the cron service on Linux can be done with /usr/sbin/cron restart, but note that cron is a system‑started daemon and will often restart automatically, so you may see “cron already running”.

Each job’s output is mailed to the user by default. For long‑running or frequent jobs, redirect output to /dev/null (e.g., >/dev/null 2>&1) to avoid filling mailboxes and generating large log files.

Overall, configuring cron on macOS involves the same steps as on Linux: verify the daemon, edit the crontab, use proper syntax, handle environment variables, and manage output redirection.