\n\n\n\n\n\n\n<\/p>
What is a cron job?<\/h2>
A cron job is a utility that lets Linux and Unix users run commands or scripts automatically at a specified time and date<\/strong>. Instead of running a command manually every day or week, you schedule it once, and the system executes it in the background at the set time.<\/p> This automation is important for server management. For example, a system administrator managing a virtual private server (VPS) cannot back up databases manually every night at 3:00 AM.<\/p> A cron job handles this task reliably, improving efficiency and reducing human error.<\/p> Common cron job use cases include:<\/p> A cron job runs through the cron daemon (crond)<\/strong>, a background service that runs continuously and executes commands defined in cron table (crontab)<\/strong> files.<\/p> Every minute, the daemon checks the configuration files and determines whether any tasks are scheduled to run at that time.<\/p> It’s important to distinguish between the two types of configuration files:<\/p> Crontab syntax defines scheduled tasks (cron jobs) using a single line with five time-and-date fields followed by the command to execute. Special operators add flexibility when you define time intervals.<\/p> Here’s the basic format of a crontab entry:<\/p> The five timing fields define when a cron job runs. The system reads the schedule in the following order:<\/p> \n\n\n Important!<\/strong> Be careful when scheduling jobs across multiple servers in different time zones. Always check each server’s local time with the date<\/strong> command to confirm your configuration is correct.<\/p><\/div>\n\n\n\n<\/p> Crontab operators let you define complex intervals and patterns within the timing fields. Cronie and its predecessor, Vixie cron, support eight operators.<\/p> These implementations serve as the default cron tools on most Linux distributions, including Ubuntu, Debian, RHEL, CentOS, and Fedora:<\/p> These operators are not supported by standard Linux cron. They work only in Java-based schedulers, such as Quartz and Spring Boot, or cloud services like AWS EventBridge:<\/p> \n\n\n Most cron implementations let you combine ranges with step values. For example, 1-20\/2<\/strong> runs a job every two minutes during the first 20 minutes.<\/p>\n <\/div>\n\n\n\n<\/p> The following examples show how to apply crontab syntax to real-world tasks.<\/p> Special strings are shortcuts that start with @ and replace the five-field syntax<\/strong>. They improve readability for common schedules and reduce the risk of syntax errors.<\/p> Here are a few examples of cron jobs using special strings:<\/p> \n\n\n Important!<\/strong> The @reboot<\/strong> directive runs when the cron daemon starts, not necessarily when the system boots. If you stop and restart the cron service without rebooting the system, @reboot<\/strong> jobs run again.<\/p><\/div>\n\n\n\n<\/p> System administrators control who can schedule cron jobs using two files in the \/etc\/<\/strong> directory: cron.allow<\/strong> and cron.deny<\/strong>.<\/p> If neither file exists, the default behavior depends on the distribution:<\/p> Always check your distribution’s documentation or test cron access with a non-root user.<\/p> For example, to allow only a database administrator (dbadmin<\/strong>) to schedule tasks, create a cron.allow<\/strong> file and add dbadmin<\/strong> to it. This setup prevents other users from running unauthorized background tasks that consume system resources.<\/p> To set up a cron job, open your machine’s terminal, confirm that cron is installed, create or edit a crontab file with crontab -e<\/strong>, and view your scheduled tasks with crontab -l<\/strong>.<\/p> Some jobs may require elevated or root privileges, or you may need to place scripts in system directories for recurring tasks.<\/p> To manage cron jobs, access your server’s command line. If you use a remote server or VPS, connect through SSH with a client such as PuTTY<\/a> on Windows or Terminal on macOS or Linux.<\/p> Alternatively, Hostinger VPS<\/a> users can use the browser terminal<\/strong> feature available in the VPS dashboard of hPanel.<\/p>\n
How does a cron job work?<\/h2>
\n
Understanding crontab syntax and operators<\/h2>
minute hour day_of_month month day_of_week command_to_execute<\/pre>
The five timing fields (minute, hour, date)<\/h3>
Field<\/strong><\/td> Description<\/strong><\/td> Allowed values<\/strong><\/td><\/tr> Minute<\/strong><\/td> The minute of the hour when the command runs.<\/td> 0–59<\/td><\/tr> Hour<\/strong><\/td> The hour of the day in 24-hour format.<\/td> 0–23<\/td><\/tr> Day of month<\/strong><\/td> The specific date of the month.<\/td> 1–31<\/td><\/tr> Month<\/strong><\/td> The month of the year.<\/td> 1–12 or JAN–DEC<\/td><\/tr> Day of week<\/strong><\/td> The day of the week.<\/td> 0–6, where Sunday = 0 (or 7 on some systems)<\/td><\/tr><\/tbody><\/table><\/figure> Crontab operators<\/h3>
\n
\n
💡 Pro tip<\/h4>\n
Cron job examples<\/h3>
Cron syntax<\/strong><\/td> Purpose<\/strong><\/td> Explanation<\/strong><\/td><\/tr> 0 0 * * 0 \/root\/backup.sh<\/strong><\/td> Weekly backup<\/td> Runs the backup script every Sunday at midnight.<\/td><\/tr> 0 * * * 1 \/root\/clearcache.sh<\/strong><\/td> Server maintenance<\/td> Clears the cache every hour, but only on Mondays.<\/td><\/tr> 0 6,18 * * * \/root\/db-dump.sh<\/strong><\/td> Database snapshot<\/td> Dumps the database twice a day at 6 AM and 6 PM.<\/td><\/tr> *\/10 * * * * \/scripts\/monitor.sh<\/strong><\/td> Uptime monitoring<\/td> Runs a monitoring script every 10 minutes.<\/td><\/tr> 0 0 1,15 * * \/scripts\/payroll.php<\/strong><\/td> Bi-monthly task<\/td> Runs a payroll script on the 1st and 15th of every month at midnight.<\/td><\/tr> 30 2 * * * \/usr\/bin\/apt update<\/strong><\/td> System update<\/td> Checks for package updates daily at 2:30 AM, which is usually a low-traffic time.<\/td><\/tr> * * * * \/scripts\/s1.sh; \/scripts\/s2.sh<\/strong><\/td> Multiple tasks<\/td> Runs multiple commands in a single cron job by separating them with a semicolon.<\/td><\/tr> 0 8 1-7 * * [ “$(date ‘+\\%u’)” = “1” ] && \/scripts\/report.sh<\/strong><\/td> Monthly report<\/td> Generates a report at 8 AM on days 1–7 of the month, but only executes the script when it’s Monday.<\/td><\/tr><\/tbody><\/table><\/figure> What are cron job special strings?<\/h2>
\n
@daily \/home\/user\/scripts\/daily-cleanup.sh\n@reboot \/usr\/local\/bin\/start-my-app.sh\n@hourly \/var\/www\/html\/monitor.php<\/pre>
Cron permissions<\/h2>
\n
\n
How to set up a cron job<\/h2>
1. Access the terminal or SSH<\/h3>
![\"Hostinger](\"https:\/\/imagedelivery.net\/LqiWLm-3MGbYHtFuUbcBtA\/wp-content\/uploads\/sites\/2\/2021\/09\/hpanel-vps-overview-terminal-highlighted.png\/public\")