Do you want to wake up at 2 a.m., clear the logs, clean temporary files, and run the same server maintenance tasks every single day?<\/p>\n
Well, me neither. Nor do the millions of server admins who manage the 14+ billion servers<\/a> across the world.<\/p>\n So, stop the madness \u2014 I beg you!<\/p>\n Cron jobs are built for that.<\/strong><\/p>\n Because, genuinely, nothing says \u201ccompetent sysadmin<\/em>\u201d like being fast asleep and taking credit for the work your scripts handle for you. It\u2019s called \u201cutilizing your resources.<\/em>\u201d<\/p>\n With cron jobs:<\/p>\n Today, you\u2019re going to become a cron jobs pro.<\/p>\n A cron job is essentially a task scheduler built into Unix-like operating systems (Linux, macOS) that lets you run Linux commands<\/a> automatically at specified times and dates.<\/p>\n Think of it like a to-do list for your server, but\u2026this one actually gets completed.<\/p>\n If your server infrastructure were a restaurant:<\/p>\n When the clock hits the scheduled time, the manager taps the assigned employee on the shoulder and says, \u201cIt\u2019s showtime!\u201d<\/p>\n The employee<\/em> then executes their task without question or complaint.<\/p>\n If only we humans were this reliable, the world would be a different place!<\/p>\n Every cron job consists of two main parts:<\/p>\n The schedule uses a specific syntax that might look like some computer wizardry at first glance:<\/p>\n But take a closer look and it\u2019ll start to make sense.<\/p>\n Each asterisk can be replaced with specific values, ranges, or intervals to create precisely the schedule you need.<\/p>\n There\u2019s a reason why server admins (even me) get misty-eyed when discussing cron jobs.<\/p>\n They turn server management into something that (at least remotely) resembles work-life balance.<\/p>\n Remember time? That thing you never have enough of? Cron jobs give it back. You set them, you forget them, and you\u2019re pretty much never looking at them.<\/p>\n (Well, until they break or you need to change the schedule.)<\/p>\n Humans are inconsistent. We forget things. We make typos. We get distracted by cat videos. Cron jobs perform the exact task, the exact same way, every single time \u2014 no exceptions.<\/p>\n With cron jobs, essential maintenance happens 24\/7\/365, whether you\u2019re awake, asleep, or on a beach sipping margaritas.<\/p>\n When you manually perform tasks, can you remember exactly what you did and exactly when you did it? Probably not.<\/p>\n But cron jobs can be configured to log their activity, creating a paper trail of all automated actions for troubleshooting and verification.<\/p>\n As your infrastructure grows, manually managing everything becomes exponentially more difficult. Cron jobs scale effortlessly.<\/p>\n Meaning, the same job can run across multiple servers without requiring additional time from you.<\/p>\n Subscribe now to receive all the latest updates, delivered directly to your inbox.<\/p>\n<\/div>\n Enough theory! You need to get your hands dirty with some practical cron job setup.<\/p>\n Most Unix-like systems have cron pre-installed. To check if it\u2019s available for use, type the below command:<\/p>\n Depending on the default editor, the command will open the crontab in your specific editor. If you have never used crontab before, it might ask you to set the default editor.<\/p>\n If the terminal responds with command not found<\/strong>, you\u2019ll need to install cron with the below commands:<\/p>\n Once done, start and enable the cron service<\/strong>:<\/p>\n With the start <\/strong>and enable <\/strong>commands, we\u2019re starting the cron service to execute the cron jobs.<\/p>\n And with enable<\/strong>, we make sure that even if your server restarts, the cron service automatically restarts with it, and no cron jobs are missed.<\/p>\n Nerd Note:<\/em><\/strong> CentOS calls the cron service \u201ccrond\u201d, so you will need to start and enable the crond service.<\/em><\/p>\n Alright, open the crontab or the crontable to begin adding your scheduled jobs.<\/p>\n Each user on the system can have their own crontab file. Additionally, there is a system-wide crontab.<\/p>\n To edit your personal crontab:<\/p>\n This opens your crontab file in your default text editor. If this is your first time, choose the nano<\/strong> editor (option 1) as it\u2019s the most beginner-friendly.<\/p>\n For system-wide crontabs, run the below command with sudo privileges<\/a>:<\/p>\n We\u2019ve already talked about the basic structure in the anatomy of cron jobs before.<\/p>\n But creating a cron job<\/a> can be confusing sometimes. Crontab.guru<\/a> helps you visualize the job schedules as you type them.<\/p>\n Now for the fun part \u2014 writing our first cron job. Let\u2019s take a look at some common cron job schedules:<\/p>\n Every minute:<\/strong><\/p>\n Every hour at minute 0:<\/strong><\/p>\n Every day at midnight:<\/strong><\/p>\n Every Monday at 3 a.m.:<\/strong><\/p>\n Every 15 minutes:<\/strong><\/p>\n First day of every month at 6:30 a.m.:<\/strong><\/p>\n Let\u2019s move to creating a simple backup cron job for your server.<\/p>\n The task below creates a backup of your website<\/a> every day at 2 a.m.<\/p>\n It will output a compressed tar archive of your website directory with the current date as the filename.<\/p>\n Now, exit the editor. In nano, press Ctrl+X and then hit Y.<\/p>\n To view your current crontab and verify your job was added:<\/p>\n That\u2019s it! Your first cron job is now set up and will run automatically at the scheduled time.<\/p>\n Now that you know the basics, let\u2019s explore some practical cron jobs that can make your life as a website manager significantly easier.<\/p>\n MySQL database backup (daily at 1 a.m.):<\/strong><\/p>\n Clean logs older than 7 days (weekly on Sundays):<\/strong><\/p>\n Check website response time every 5 minutes:<\/strong><\/p>\n Fetch and update dynamic content (every hour):<\/strong><\/p>\n Send a weekly traffic summary every Monday at 9 a.m.:<\/strong><\/p>\n Run a security scan script every night at 3 a.m.:<\/strong><\/p>\n To make sure your cron jobs run smoothly and don\u2019t cause more problems than they solve, here are some important best practices.<\/p>\n Add comments to explain each job \u2014 Future you will thank present you for documenting what each cron job does and why.<\/p>\n Consider using lockfiles for long-running jobs to prevent a new instance from starting if the previous one is still running.<\/p>\n The only time you have to look back at a cron job is when it breaks \u2014 and when it breaks, here\u2019s how to diagnose and fix common issues.<\/p>\n Symptoms:<\/strong> Your scheduled task doesn\u2019t seem to be executing at all.<\/p>\n Potential fixes:<\/strong><\/p>\n Symptoms:<\/strong> The job executes but doesn\u2019t complete its task successfully.<\/p>\n Potential fixes:<\/strong><\/p>\n Symptoms:<\/strong> Your inbox is flooded with cron output emails.<\/p>\n Potential fixes:<\/strong><\/p>\n Only email on errors:<\/p>\n Symptoms:<\/strong> Jobs run at unexpected times or frequencies.<\/p>\n Potential fixes:<\/strong><\/p>\n We\u2019ve looked at the basics, and you are pretty much a pro with cron jobs by now. But this section will take you a step further.<\/p>\n You don\u2019t always need to write cron jobs with those asterisk signs. There are some special strings that let you set up cron jobs quite easily.<\/p>\n For example, if you want something to run daily, just write the below command:<\/strong><\/p>\n To avoid repeating a string over and over again in your cron jobs (for example, a specific path, or your admin email), set up environment variables<\/a> at the beginning of your crontab.\u00a0<\/p>\n You can then reuse the variables as required within your scripts or commands.<\/p>\n If we use the environment variable MAILTO<\/strong> in our mailing_script.sh<\/strong>, the script will automatically send an email to the correct email address.<\/p>\n With this, changing the admin email will only require changing the value of the MAILTO variable, instead of making changes across all scripts.<\/p>\n If you have superuser access<\/a>, you can edit another user\u2019s crontab:<\/p>\n Unlike cron, anacron ensures jobs run even if the computer was off during the scheduled time:<\/p>\n Edit \/etc\/anacrontab<\/strong> to add jobs that will run when the system comes back online.<\/p>\n Run jobs in sequence:<\/p>\n For serious server management, consider tools like Cronitor<\/a> that provide monitoring and alerts for your cron jobs.<\/p>\n Cron jobs can\u2019t exist in isolation. They need a server and a service running on a server that you need to manage.\u00a0<\/p>\n Now, if you\u2019re reading this article, it\u2019s highly likely that you have a server for your website or application.\u00a0<\/p>\n In fact, if you\u2019re hosting with DreamHost VPS or any Linux-based hosting provider<\/a>, you\u2019ve already got everything you need to get started with automating your server management tasks.\u00a0<\/p>\n\n
First, What\u2019s a Cron Job? (The Not-Boring Version)<\/h2>\n
Cron in Metaphors<\/h3>\n
\n
The Anatomy of a Cron Job<\/h3>\n
\n
![\"\"](\"https:\/\/www.dreamhost.com\/blog\/wp-content\/uploads\/2025\/05\/01_anatomy_of_a_crontab.webp\")
<\/figure>\nWhy Server Admins Love Cron Jobs<\/h2>\n
1. They Save You Time<\/h3>\n
2. They Maintain Consistency<\/h3>\n
3. Your Server Never Sleeps<\/h3>\n
4. Error Logs > Human Memory<\/h3>\n
5. They\u2019re Built for Scalability<\/h3>\n
Get Content Delivered Straight to Your Inbox<\/h2>\n
Setting Up Cron Jobs: A Step-by-Step Guide<\/h2>\n
Step 1: Confirm Cron Is Installed<\/h3>\n
crontab -e<\/code><\/pre>\n![\"\"](\"https:\/\/www.dreamhost.com\/blog\/wp-content\/uploads\/2025\/05\/02_confirm_cron_is_installed.webp\")
<\/figure>\n\n
sudo apt update && sudo apt install cron<\/code><\/li>\nsudo yum install cronie<\/code><\/li>\n<\/ul>\nsudo systemctl start cron\nsudo systemctl enable cron<\/code><\/pre>\nStep 2: Understanding the Crontab<\/h3>\n
crontab -e<\/code><\/pre>\nsudo nano \/etc\/crontab<\/code><\/pre>\n![\"\"](\"https:\/\/www.dreamhost.com\/blog\/wp-content\/uploads\/2025\/05\/03_understanding_the_crontab-1024x519.webp\")
<\/figure>\nStep 3: Cron Job Syntax<\/h3>\n
![\"\"](\"https:\/\/www.dreamhost.com\/blog\/wp-content\/uploads\/2025\/05\/04_crontab_guru.webp\")
<\/figure>\n* * * * \/path\/to\/command<\/code><\/p>\n0 * * * * \/path\/to\/command<\/code><\/p>\n0 0 * * * \/path\/to\/command<\/code><\/p>\n0 3 * * 1 \/path\/to\/command<\/code><\/p>\n*\/15 * * * * \/path\/to\/command<\/code><\/p>\n30 6 1 * * \/path\/to\/command<\/code><\/p>\nStep 4: Creating Your First Cron Job<\/h3>\n
0 2 * * * tar -czf \/path\/to\/backup\/website-backup-$(date +%Y%m%d).tar.gz \/path\/to\/your\/website<\/code><\/p>\nStep 5: Save and Verify<\/h3>\n
crontab -l<\/code><\/pre>\n![\"\"](\"https:\/\/www.dreamhost.com\/blog\/wp-content\/uploads\/2025\/05\/05_save_and_verify.webp\")
<\/figure>\nPractical Cron Job Examples for Website Managers<\/h2>\n
Database Backups<\/h3>\n
0 1 * * * mysqldump -u username -p'password' database_name | gzip > \/path\/to\/backups\/db-backup-$(date +%Y%m%d).sql.gz<\/code><\/pre>\nLog Rotation and Cleanup<\/h3>\n
0 0 * * 0 find \/path\/to\/logs -type f -name \"*.log\" -mtime +7 -delete<\/code><\/pre>\nWebsite Performance Monitoring<\/h3>\n
*\/5 * * * * curl -o \/dev\/null -s -w \"%{http_code} %{time_total}sn\" example.com >> \/path\/to\/logs\/website-performance.log<\/code><\/pre>\nContent Updates<\/h3>\n
0 * * * * \/path\/to\/content-update-script.sh<\/code><\/pre>\nEmail Reports<\/h3>\n
0 9 * * 1 \/path\/to\/generate-and-email-report.sh<\/code><\/pre>\nSecurity Scans<\/h3>\n
0 3 * * * \/path\/to\/security-scan.sh<\/code><\/pre>\nCron Job Best Practices: Dos and Don\u2019ts<\/h2>\n
The Dos<\/h3>\n
\n
\u201c\/usr\/bin\/python\u201d<\/code> is better than just python.<\/li>\n>\/dev\/null 2>&1<\/code> to suppress output or redirect to a log file instead.<\/li>\nDaily database backup - Added by Jane on 2023-05-15\n0 1 * * * \/path\/to\/backup-script.sh<\/code><\/pre>\n0 * * * * flock -n \/tmp\/script.lock \/path\/to\/your\/script.sh<\/code><\/pre>\nThe Don\u2019ts<\/h3>\n
\n
\u201c.\/script.sh\u201d<\/code> will almost certainly fail in cron.<\/li>\nWhat To Do When Cron Jobs Go Wrong<\/h2>\n
Common Problem #1: Job Doesn\u2019t Run<\/h3>\n
\n
Common Problem #2: Job Runs But Fails<\/h3>\n
\n
* * * * \/path\/to\/script.sh > \/path\/to\/script.log 2>&1<\/code><\/li>\nCommon Problem #3: Email Flooding<\/h3>\n
\n
>\/dev\/null 2>&1<\/code><\/li>\n>\/path\/to\/logfile.log 2>&1<\/code><\/li>\n<\/ul>\n* * * * \/path\/to\/script.sh >\/dev\/null || echo \"Script failed\" | mail -s \"Cron failure\" you@example.com<\/code><\/pre>\nCommon Problem #4: Timing Issues<\/h3>\n
\n
Advanced Cron Job Writing Techniques<\/h2>\n
Using Special Strings<\/h3>\n
\n
@daily \/path\/to\/daily-backup.sh<\/code><\/pre>\nEnvironment Variables in Crontab<\/h3>\n
SHELL=\/bin\/bash\nPATH=\/usr\/local\/sbin:\/usr\/local\/bin:\/usr\/sbin:\/usr\/bin:\/sbin:\/bin\nMAILTO=admin@example.com\n\n# This job will send errors to admin@example.com\n0 2 * * * \/path\/to\/mailing_script.sh<\/code><\/pre>\nRunning Jobs As Different Users<\/h3>\n
sudo crontab -u username -e<\/code><\/pre>\nUsing Anacron for Machines That Aren\u2019t Always On<\/h3>\n
sudo apt install anacron<\/code><\/pre>\nJob Chaining for Complex Workflows<\/h3>\n
0 1 * * * \/path\/to\/first-script.sh && \/path\/to\/second-script.sh<\/code><\/pre>\nMonitoring Cron Jobs\u00a0<\/h3>\n
0 * * * * cronitor exec check-12345 -- \/path\/to\/your\/script.sh<\/code><\/pre>\nLet\u2019s Talk Costs<\/h2>\n