Thrum

What is cron, 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.

cron is the classic Unix scheduler: it reads crontab files and runs the commands in them at set times. On macOS, launchd starts cron only when /etc/crontab or a user crontab in /usr/lib/cron/tabs exists, so if it is running, someone or some software added a scheduled job. Its own CPU use is tiny; anything heavy is the command it starts.

cron at a glance

cron
Made byApple (part of macOS, Vixie Cron)
TypeSystem daemon
Location/usr/sbin/cron
Runs asroot
Started bylaunchd job com.vix.cron
Can you quit it?Not usefully. launchd starts it again while a crontab exists. Remove the crontab entries instead.

What is cron?

Its man page says cron is launched by launchd when it sees /etc/crontab or files in /usr/lib/cron/tabs. It loads every crontab, wakes up every minute, and runs each command whose time has come. Any output from a command is mailed to the crontab's owner on the Mac.

The launchd job is com.vix.cron, named after Paul Vixie, the author of this cron. It is kept alive while /etc/crontab exists and is started when files appear in the tabs folder. On macOS, launchd jobs are the system's own way of scheduling, and cron is kept for compatibility.

Is cron safe?

cron itself is an Apple-signed program in /usr/sbin. What matters is what it runs: the commands in the crontabs. Developer tools, backup scripts and some management software add cron jobs; malware has used them too, so check the entries if you did not add them.

Why does cron use so much CPU and disk?

How much CPU is normal for cron?

cron itself should show near 0% CPU, with a brief wake each minute. Load from its jobs belongs to the commands it starts.

On a Mac with no crontabs, cron is normally not running.

How do you see and remove cron jobs on a Mac?

  1. List your own cron jobs. In Terminal, run crontab -l. It prints your crontab, or says there is none.
  2. Check the system crontab. Run cat /etc/crontab. On a default Mac the file does not exist.
  3. Check other users' crontabs. Run sudo ls /usr/lib/cron/tabs. Each file is named after the account it belongs to; sudo crontab -l -u <name> shows one.
  4. Edit or remove entries. Run crontab -e to edit your crontab, or crontab -r to remove it entirely. Once no crontab is left, launchd stops running cron.

When should you worry about cron?

Worry about cron entries you did not add that download or run files from unusual places, such as hidden folders or /tmp. Remove them and look for the software that created them.

cron that stays busy itself, rather than its commands, is not expected.

How do you check cron in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type cron in the search field. The CPU tab shows its % CPU. The Disk tab shows its Bytes Written and Bytes Read. Double-click the row for its parent process, memory details and open files.

In Terminal, the first command lists every cron process with its PID, user, CPU and memory (RSS is resident memory in kilobytes). fs_usage prints each file it reads or writes until you press Control-C; it needs an administrator password.

ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'cron' | grep -v grep
sudo fs_usage -w -f filesys cron

How can Thrum help with cron?

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 cron 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 cron

Should I use cron or launchd on a Mac?

Both work. launchd is macOS's native scheduler and can run missed jobs after sleep; cron is kept for compatibility with Unix scripts.

Why is cron running when I never set up a cron job?

Some installed software created a crontab. The steps above show which one.

Sources