What is atrun, and why is it running on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.
atrun is the macOS program that runs commands queued for later with the at and batch commands. Its launchd job is disabled by default, so atrun never runs unless an administrator enabled it. When enabled, launchd starts it every 30 seconds to start any queued jobs whose time has come.
atrun at a glance
| atrun | |
|---|---|
| Made by | Apple (part of macOS) |
| Type | System daemon (disabled by default) |
| Location | /usr/libexec/atrun |
| Runs as | root |
| Started by | launchd job com.apple.atrun |
| Can you quit it? | It is disabled by default. If enabled, launchd runs it every 30 seconds; disable the job instead of quitting it. |
What is atrun?
The at command schedules a one-off command for a later time, and batch queues one to run when the system is not busy. The atrun man page says it runs the commands queued by at, is invoked periodically by launchd as specified in com.apple.atrun.plist, and that the property list contains Disabled set to true, so atrun is never invoked by default.
When enabled, each run starts all due jobs in the lowercase queues, and at most one batch job if the one-minute load average is below the set limit. Before starting a job it checks the owner's account with PAM and refuses to run it if the account is locked or expired. The job's StartInterval on macOS 26.3.1 is 30 seconds.
Is atrun safe?
Yes, atrun is an Apple-signed program in /usr/libexec. If it runs, someone enabled it with administrator rights. The jobs it runs are what to check.
Why does atrun use so much CPU?
- Queued jobs. The commands queued with at or batch run as their own processes when their time comes. Their CPU use belongs to them, not to atrun.
- A run every 30 seconds. Once enabled, launchd starts atrun every 30 seconds to check the queue. Each run is brief.
- Batch jobs waiting for low load. Batch jobs only start when the load average is low, so they may start later than expected on a busy Mac.
How much CPU is normal for atrun?
On a default Mac atrun never runs. If enabled, short appearances every 30 seconds at near 0% CPU are normal.
Heavy load is from the queued commands.
How do you check atrun and its queued jobs?
- List queued jobs. In Terminal, run
atqto list pending jobs, andat -c <job number>to see what one runs. - Remove a job. Run
atrm <job number>to delete a queued job. - Check whether atrun is enabled. Run
launchctl print-disabled system | grep atrun. An entry marked enabled means someone turned it on. - Disable it again. Run
sudo launchctl disable system/com.apple.atrunand restart the Mac.
When should you worry about atrun?
Worry if atrun is enabled and you did not do it, and atq lists jobs you do not recognize. Remove them and check for other unexpected scheduled tasks in cron and launchd.
A copy outside /usr/libexec would not be Apple's.
How do you check atrun in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type atrun in the search field. The CPU tab shows its % CPU. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every atrun process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'atrun' | grep -v grep
How can Thrum help with atrun?
Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when atrun is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. macOS does not let apps quit processes owned by root or other users, so Thrum shows them for information and leaves stopping them to the steps above.
Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.
Questions about atrun
Why does the at command not work on my Mac?
Because atrun is disabled by default. Jobs can be queued, but nothing runs them until the com.apple.atrun job is enabled.
Is atrun the same as cron?
No. cron runs repeating schedules from crontab files; atrun runs one-off jobs queued with at and batch.
Sources
- atrun(8) man page: run man atrun in Terminal
- at(1) man page: run man at in Terminal