Useful Linux cron examples

Hey everyone! If you're like me, you probably want to automate those repetitive tasks on your Linux machine. Learning about cron jobs was a game-changer for my workflow. It felt a bit intimidating at first, but once I got the hang of it, I realized how powerful and simple it is! I'm excited to share a comprehensive list of common crontab examples that I've found incredibly useful for various scheduling needs. So, what exactly is cron? It's a time-based job scheduler in Unix-like operating systems. Crontab (short for 'cron table') is the file where you schedule these commands. Think of it as your personal assistant who runs tasks exactly when you tell them to, without you lifting a finger! This crontab list will walk you through the expressions and commands to get started. The basic crontab syntax might look like a secret code at first, but it's super logical once you break it down. Each line in your crontab file has five time fields, followed by the command you want to run: minute (0-59) hour (0-23) day_of_month (1-31) month (1-12) day_of_week (0-7, 0 or 7 is Sunday) command_to_execute To make scheduling even more flexible, cron uses a few special characters: *: Any value (e.g., * in the minute field means 'every minute'). ,: List (e.g., 1,15,30 in the minute field means 'at minutes 1, 15, and 30'). -: Range (e.g., 9-17 in the hour field means 'from 9 AM to 5 PM'). /: Step (e.g., */5 in the minute field means 'every 5 minutes'). Now, let's dive into some practical cron expressions with corresponding commands and descriptions for common tasks: Run a task every minute: * * * * * /path/to/your_script.sh *My personal use*: This is great for quick checks, like monitoring a log file or a service's uptime every minute. Run a task every 5 minutes: */5 * * * * /path/to/another_script.sh Run a task hourly: 0 * * * * /path/to/hourly_backup.sh You can also use the special string @hourly. *I often use @hourly for tasks like rotating logs or making small incremental backups.* Run a task daily at a specific time (e.g., 3:00 AM): 0 3 * * * /path/to/daily_report.sh Alternatively, use @daily. *This is perfect for those daily reports or database cleanups you don't want to do manually.* Run a task weekly (e.g., every Monday at 1:00 AM): 0 1 * * 1 /path/to/weekly_maintenance.sh Or use @weekly. *My weekly system updates and security scans usually run with this setting.* Run a task monthly (e.g., on the 1st of every month at midnight): 0 0 1 * * /path/to/monthly_cleanup.sh Or use @monthly. *I schedule my monthly data archives or billing reports with this one.* Run a task yearly (e.g., on January 1st at midnight): 0 0 1 1 * /path/to/yearly_archive.sh Or use @yearly (or @annually). *This is handy for annual data consolidation or fiscal year-end reports.* Run a task at system startup: @reboot /path/to/start_service.sh *This is a lifesaver for making sure certain services or scripts start automatically after a server reboot, ensuring everything is up and running without manual intervention.* A pro-tip I learned the hard way: Always handle your script's output! Otherwise, cron might email you for every single output, or your logs will be messy. You can redirect output to a log file or null: * * * * * /path/to/script.sh >> /var/log/my_cron.log 2>&1 (Appends output to a log file) * * * * * /path/to/script.sh > /dev/null 2>&1 (Discards all output) To get started, just type crontab -e in your terminal. This opens your personal crontab file for editing. And crontab -l will list your current cron jobs. Remember to save and exit the editor, and your new cron job will be active immediately! Hopefully, this crontab list of examples gives you a solid starting point for automating your Linux tasks. It’s incredibly satisfying to set something up once and know it’ll just run in the background. Happy scheduling!