Cron vs At Command
0 */2 * * *Every 2 hours
Next 10 Executions
Times shown in UTC
- Mon, May 18, 202610:00
- Mon, May 18, 202612:00
- Mon, May 18, 202614:00
- Mon, May 18, 202616:00
- Mon, May 18, 202618:00
- Mon, May 18, 202620:00
- Mon, May 18, 202622:00
- Tue, May 19, 202600:00
- Tue, May 19, 202602:00
- Tue, May 19, 202604:00
Field Breakdown
0*/2***About This Schedule
Cron and at serve different scheduling needs. Cron runs jobs on a recurring schedule — every 5 minutes, daily at midnight, weekly on Monday. At runs a job once at a specific future time — "at 3pm tomorrow" or "at noon next Friday."
Use at when you need a one-time delayed execution: scheduling a server restart during a maintenance window, sending a reminder at a specific time, running a migration at 2 AM tonight, or delaying a deployment by 30 minutes. The command is simple: echo "backup.sh" | at 02:00 tomorrow.
Use cron when you need recurring automation. If you find yourself creating repeated at jobs for the same task, that's a sign you should use cron instead. The two tools complement each other: cron for recurring schedules, at for one-off future tasks.