How to Manage Cron Job Email Output
By default cron emails you the output of every run, which floods your inbox. The goal is to hear about errors but not routine successes.
Step-by-step
- Set the notification address. Advanced → Cron Jobs → enter your email at the top so failures can reach you.
- Silence routine output by appending to the command:
>/dev/null 2>&1— this discards both normal and error output. - To get errors only (recommended), append just
>/dev/null— normal output is discarded but errors still email you. - To keep a log instead of emails, append
>> /home/youruser/cron.log 2>&1to write output to a file you can review. - Edit the job to apply your chosen redirect and save.
- Check behaviour after the next run — confirm you only receive what you intended.
💡 Good to know
- Use ">/dev/null" (errors only) on healthy recurring jobs — silence success, surface problems.
- A log file is better than email for frequent jobs; review and truncate it occasionally.
- No emails AND no log means you will not know if a job fails — keep at least one signal.