Understanding cron, crond, and crontab: Linux Scheduled Task Management
This article explains Linux's cron daemon, the crond service, and the crontab command, detailing their roles, usage syntax, scheduling format, special symbols, and how to manage and verify scheduled tasks on a Linux system.
On Linux, periodic tasks are handled by the cron daemon, which starts with the system and reads its configuration into memory, operating as a timed execution service without user intervention.
The crond service is the actual scheduler that runs after the OS boots; it checks every minute for jobs to execute and runs them automatically.
The crontab command is used to interact with the cron service. Common options include:
crontab [-u username] [-l|-e|-r] - -u : only root can manage other users' crontabs. - -e : edit the crontab file. - -l : list current crontab entries. - -r : remove all entries (use -e to delete a single entry).
A crontab entry consists of six fields: five time specifications followed by the command to run. The basic format is * * * * * cmd , where the fields represent minute (0‑59), hour (0‑23), day of month (1‑31), month (1‑12), and day of week (0‑7, with 0 and 7 both meaning Sunday).
Special symbols can be used in the time fields:
* – any value (every unit). - – range, e.g., 17-19 means 17, 18, and 19. , – list, e.g., 17,18,19 . / – step, e.g., */10 means every 10 minutes.
After editing the crontab, the system usually reloads automatically; if a manual restart is needed, locate the crond binary with whereis crond and run crond restart or check its status with crond status . Verify the daemon is running using ps -ef | grep -i crond | grep -v grep .
360 Quality & Efficiency
360 Quality & Efficiency focuses on seamlessly integrating quality and efficiency in R&D, sharing 360’s internal best practices with industry peers to foster collaboration among Chinese enterprises and drive greater efficiency value.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.