What is at Command?
A Unix utility that schedules a one-time command to run at a specific future time.
Definition
The "at" command is a Unix/Linux utility for scheduling one-time tasks at a specific date and time. Unlike cron, which handles recurring schedules, "at" is designed for single executions: "at 3pm tomorrow" runs a command once at that exact time. It reads commands from standard input and queues them for the "atd" daemon. Variants include "batch" (runs when system load is low) and "atq" (lists pending jobs).
Simple Analogy
Like setting a single alarm on your phone — it goes off once at the specified time and never repeats, unlike a recurring alarm that rings every day.
Why It Matters
Not every scheduled task needs to recur. One-time jobs — deployment scripts, data migrations, timed announcements — are better served by "at" than by creating a cron job that must be manually removed afterward. Understanding "at" helps you choose the simplest scheduling tool for each task and reduces crontab clutter.
How to Verify
Run "at -l" or "atq" to list pending one-time jobs. Check if the "atd" daemon is running with "systemctl status atd". On systems where "at" is not installed, use your package manager: "apt install at" on Debian/Ubuntu or "yum install at" on RHEL/CentOS.
Common Mistakes
Using cron for one-time tasks and forgetting to remove the entry afterward. Not verifying that the "atd" daemon is running before scheduling jobs. Specifying ambiguous time formats — "at 3pm" works, but complex date strings vary across implementations.
Best Practices
Use "at" for genuinely one-time tasks and cron for recurring ones. For web-based one-time scheduling, CronJobPro supports one-time schedules that automatically deactivate after execution, combining the simplicity of "at" with the reliability of a managed service.
Cron Expression Generator
Build your cron expression
Try it free →Frequently Asked Questions
What is at Command?
The "at" command is a Unix/Linux utility for scheduling one-time tasks at a specific date and time. Unlike cron, which handles recurring schedules, "at" is designed for single executions: "at 3pm tomorrow" runs a command once at that exact time. It reads commands from standard input and queues them for the "atd" daemon. Variants include "batch" (runs when system load is low) and "atq" (lists pending jobs).
Why does at Command matter for cron jobs?
Not every scheduled task needs to recur. One-time jobs — deployment scripts, data migrations, timed announcements — are better served by "at" than by creating a cron job that must be manually removed afterward. Understanding "at" helps you choose the simplest scheduling tool for each task and reduces crontab clutter.
What are best practices for at Command?
Use "at" for genuinely one-time tasks and cron for recurring ones. For web-based one-time scheduling, CronJobPro supports one-time schedules that automatically deactivate after execution, combining the simplicity of "at" with the reliability of a managed service.
Related Terms
Cron
A time-based job scheduler built into Unix and Linux operating systems.
One-Time Schedule
A job configured to execute exactly once at a specific future date and time.
Cron Daemon
The background process that continuously checks and executes scheduled cron jobs.
Schedule
A defined plan that determines when and how often a job runs.