When to use at
Use at to schedule a one-time task rather than a recurring job. The task runs later without your interactive shell, so use explicit paths and verify which environment and account will execute it.
Syntax
at [PARAMETERS] TIMESquare brackets mark optional arguments; an ellipsis means repetition. Replace example file names, user names and server addresses with your own values.
Common options and arguments
Usage examples
Schedule a test job five minutes from now
printf '%s\n' 'date >> /tmp/terminalus-at.log' | at now + 5 minutesA short logging task is scheduled for five minutes later; the at service must be available.
View your queued jobs
at -lQueued jobs owned by the account are listed for review.
Check service availability
systemctl status atdThe scheduler service is inspected without changing its state.
Notes and limitations
- To execute, you need a working atd; The service and package name depend on the distribution.
- The task is executed later with the saved environment and outside the interactive terminal; specify paths explicitly.
Common questions and troubleshooting
Why did a queued task not run?
Check the scheduler service, account restrictions and job output. Commands depending on an interactive shell environment may need explicit paths or variables.
Does at repeat a task every day?
No. Each job is scheduled once. Use a suitable recurring scheduler when repetition is intended.
Further help
Options vary by version and distribution. Check the installed documentation with this command: man at.