Close Menu
    Facebook X (Twitter) Instagram
    TecAdmin
    • Home
    • FeedBack
    • Submit Article
    • About Us
    Facebook X (Twitter) Instagram
    TecAdmin
    You are at:Home»Linux Commands»Crontab in Linux: 20 Useful Examples for Scheduling Tasks

    Crontab in Linux: 20 Useful Examples for Scheduling Tasks

    By RahulJanuary 10, 20248 Mins Read

    Are you struggling to maintain and execute cron jobs on your Linux server with optimal frequency? As a dedicated system administrator or a savvy engineer, managing cron jobs can often be a recurring task in your day-to-day responsibilities. Understanding and remembering the syntax for configuring a new cron job can be a challenge, but it’s crucial for efficient server management.

    Cron jobs are a fundamental component of server maintenance, providing a reliable method to automate repetitive tasks. Whether you’re working with CentOS, RHEL, or another Linux distribution, the crontab command is your go-to tool for editing and managing these jobs. Although the process of creating a cron job might seem straightforward, complexities can arise when juggling multiple users and diverse server environments. Fortunately, the crontab syntax is largely uniform across different Linux systems, enabling you to master task scheduling quickly.

    This in-depth tutorial is tailored for system administrators and IT professionals looking to enhance their server management skills. You’ll discover 20 examples of using crontab for scheduling jobs, ranging from basic to advanced scenarios. Additionally, learn how to use the crontab for one-time future tasks, though for such requirements, the Linux ‘at’ command is often recommended.

    Understanding Linux Crontab Syntax and Configuration

    A crontab file’s format is deceptively simple: each line comprises six fields, delineated by spaces. These fields specify the minute (0-59), hour (0-23), day of the month (1-31), and so forth, determining when the job will execute. Wildcards, like asterisks, offer additional flexibility in scheduling.

     
    [Minute] [Hour] [Day_of_the_Month] [Month_of_the_Year] [Day_of_the_Week] [Command to Execute]
    
    

    Crontab in Linux with Examples

    Here’s a quick reference for crontab scheduling:

    • Minute: Range 0-59
    • Hour: Range 0-23
    • Day of the Month: Range 1-31
    • Month of the Year: Range 1-12 or abbreviations (e.g., Jan, Feb)
    • Day of the Week: Range 0-7 (0 and 7 for Sunday)

    Moreover, we’ll delve into how to set multiple values or ranges in your cron jobs, enhancing your server’s operational efficiency.

    • Asterisks (*): For universal matching
    • Multiple Values: Use commas for distinct values (e.g., 2,4,8)
    • Range Definition: Specify ranges with a hyphen (e.g., 1-10)
    • Multiple Ranges: Combine ranges with commas (e.g., Jan-Mar, Jul-Sep)

    Stay tuned as we explore the nuances of cron job scheduling and management, ensuring your Linux servers operate smoothly and efficiently.

    How to Add/Update Crontab

    Crontab files are typically stored in the /etc/cron.d/ directory on Linux systems. The crontab command can be used to edit the crontab file.

    crontab -e 
    

    By default, it will edit the crontab entries of the currently logged-in user. To edit other user crontab use the command below:

    crontab -u username -e 
    

    Change the EDITOR environment variable to change your default editor.

    How to List Crontab

    To view the crontab entries of current users use the following command.

    crontab -l 
    

    Use -u followed by the username to view the crontab entries of the specified user.

    crontab -u username -l 
    

    20 Useful Examples for Scheduling Crontab

    Here is the list of examples for scheduling cron jobs in a Linux system using crontab.

    1. Schedule a cron to execute at 2 am daily.
    2. This will be useful for scheduling database backups on a daily basis.

      0 2 * * * bash /script/backup.sh
      
      • Asterisk (*) is used for matching all the records.
    3. Schedule a cron to execute twice a day.
    4. The below example command will execute at 5 AM and 5 PM daily. You can specify multiple time stamps by comma-separated.

      0 5,17 * * * /scripts/script.sh
      
    5. Schedule a cron to execute every minute.
    6. Generally, we don’t require any script to execute every minute but in some cases, you may need to configure it.

      * * * * *  /scripts/script.sh
      
    7. Schedule a cron to execute every Sunday at 5 PM.
    8. This type of cron is useful for doing weekly tasks, like log rotation, etc.

      0 17 * * sun  /scripts/script.sh
      
    9. Schedule a cron to execute every 10 minutes.
    10. If you want to run your script at 10 minutes intervals, you can configure it like the below. These types of crons are useful for monitoring.

      */10 * * * * /scripts/monitor.sh
      

      */10: means to run every 10 minutes. Same as if you want to execute on every 5 minutes use */5.

    11. Schedule a cron to execute on selected months.
    12. Sometimes we are required to schedule a task to be executed for selected months only. Below example script will run in January, May, and August months.

      * * * jan,may,aug *  /script/script.sh
      
    13. Schedule a cron to execute on selected days.
    14. If you required scheduling a task to be executed for selected days only. The below example will run on each Sunday and Friday at 5 PM.

      0 17 * * sun,fri  /script/script.sh
      
    15. Schedule a cron to execute on the first Sunday of every month.
    16. To schedule a script to execute a script on the first Sunday only is not possible by time parameter, But we can use the condition in command fields to do it.

      0 2 * * sun  [ $(date +%d) -le 07 ] && /script/script.sh
      
    17. Schedule a cron to execute every four hours.
    18. If you want to run a script on 4 hours intervals. It can be configured like below.

      0 */4 * * * /scripts/script.sh
      
    19. Schedule a cron to execute twice every Sunday and Monday.
    20. To schedule a task to execute twice on Sunday and Monday only. Use the following settings to do it.

      0 4,17 * * sun,mon /scripts/script.sh
      
    21. Schedule a cron to execute every 30 Seconds.
    22. To schedule a task to execute every 30 seconds is not possible by time parameters, But it can be done by scheduling the same cron twice as below.

      * * * * * /scripts/script.sh
      * * * * *  sleep 30; /scripts/script.sh
      
    23. Schedule multiple tasks in a single cron.
    24. To configure multiple tasks with a single cron Can be done by separating tasks by the semicolon ( ; ).

      * * * * * /scripts/script.sh; /scripts/scrit2.sh
      
    25. Schedule tasks to execute yearly ( @yearly ).
    26. @yearly timestamp is similar to “0 0 1 1 *“. It will execute a task on the first minute of every year, It may useful to send new year greetings 🙂

      @yearly /scripts/script.sh
      
    27. Schedule tasks to execute monthly ( @monthly ).
    28. @monthly timestamp is similar to “0 0 1 * *“. It will execute a task in the first minute of the month. It may useful to do monthly tasks like paying the bills and invoicing to customers.

      @monthly /scripts/script.sh
      
    29. Schedule tasks to execute Weekly ( @weekly ).
    30. A @weekly timestamp is similar to “0 0 * * sun“. It will execute a task in the first minute of the week. It may useful to do weekly tasks like the cleanup of the system etc.

      @weekly /bin/script.sh
      
    31. Schedule tasks to execute daily ( @daily ).
    32. @daily timestamp is similar to “0 0 * * *“. It will execute a task in the first minute of every day, It may useful to do daily tasks.

      @daily /scripts/script.sh
      
    33. Schedule tasks to execute hourly ( @hourly ).
    34. @hourly timestamp is similar to “0 * * * *“. It will execute a task in the first minute of every hour, It may useful to do hourly tasks.

      @hourly /scripts/script.sh
      
    35. Schedule tasks to execute on system reboot ( @reboot ).
    36. @reboot is useful for those tasks which you want to run on your system startup. It will be the same as system startup scripts. It is useful for starting tasks in the background automatically.

      @reboot /scripts/script.sh
      
    37. Redirect Cron Results to a specified email account.
    38. By default, cron sends details to the current user where cron is scheduled. If you want to redirect it to your other account, can be done by setup the MAIL variable like below

      crontab -l 
      
      MAIL=bob
      0 2 * * * /script/backup.sh
      
    39. Take a backup of all cron to a plain text file.
    40. I recommend keeping a backup of all jobs entry in a file. This will help you to recover cron in case of accidental deletion.

      Check current scheduled cron:

      crontab -l 
      
      MAIL=rahul
      0 2 * * * /script/backup.sh
      

      Backup cron to text file:

      # crontab -l > cron-backup.txt
      # cat cron-backup.txt
      MAIL=rahul
      0 2 * * * /script/backup.sh
      

      Removing current scheduled cron:

      # crontab -r
      # crontab -l
      no crontab for root
      

      Restore crons from text file:

      # crontab cron-backup.txt
      # crontab -l
      MAIL=rahul
      0 2 * * * /script/backup.sh
      

    Hope these examples helps you to understand the Crontab architecture and job scheduling. You can also visit another article containing more Crontab practical examples.

    Conclusion

    In conclusion, this tutorial offers an invaluable guide for both beginners and seasoned Linux users. Through 20 detailed examples, this article has illuminated the versatility and efficiency of crontab in managing routine tasks, thereby enhancing productivity and ensuring consistent execution of important jobs.

    The journey through various cron job setups, from basic to advanced configurations, demonstrates how crontab can be tailored to fit a wide array of requirements. Whether it’s automating system maintenance, managing backups, or scheduling regular data processing tasks, crontab stands out as an essential tool in the Linux arsenal. The practical nature of the examples provided ensures that readers can directly apply these concepts in their daily operations.

    Remember, mastering crontab is not just about automating tasks; it’s about optimizing your time and resources, which is crucial in the fast-paced world of technology.

    crontab crontab examples Linux crontab schedule task in crontab setup cron in linux setup task scheduling with crontab what is crontab
    Share. Facebook Twitter Pinterest LinkedIn Tumblr Email WhatsApp

    Related Posts

    Linux: A Guide to Extracting Lines Between Matching Patterns

    Grep: Display N Lines Before and After Your Search Matches

    Searching Text in Files on Linux: A Comprehensive Guide

    View 76 Comments

    76 Comments

    1. Piet Keizer on January 15, 2024 12:51 pm

      Fantastic page

      Reply
    2. Adhilsom on August 31, 2022 6:14 am

      Thanks for article here, buta

      This is the correct:
      @weekly timestamp is similar to “0 0 * * sun“

      For Linux the first day is SUNDAY when we have @weekly in crontab.

      Reply
      • Rahul on August 31, 2022 6:47 am

        Thanks Adhilsom, I have corrected it.

        Reply
    3. SandeepD on September 16, 2021 3:37 pm

      Hi Rahul
      Nice artical, Thanks a lot

      Personal request : Can you provide any guidelines regarding how to write cron job scripts for various occasions like
      payment remainders, subscription remainder, birthday wishes, backup activities and block premium users if they fail to follow the rules etc

      Thanks

      Reply
    4. Kevin on April 13, 2021 2:40 am

      Great article Rahul. Very nicely explained. I have scheduled a python script to start at 1800 hours everyday which runs in a continuous loop until stopped. Now i want to schedule a stop of the script at 0600 hours everyday. How can i do that using corntab,
      What i tried
      0 06 * * * killall -9 myscript.py

      and also
      0 6 * * * /home/pi/ killall -9 myscript.py

      also
      0 6 * * * killall -9 /home/pi/myscript.py
      However, it is not working. Please help.
      Thanks

      Reply
    5. Eddy on April 6, 2021 9:27 am

      Hello, I am on SUSE Linux Enterprise Server 12 SP4 or 15 SP2 and when I try to cron script every specific sunday of the month, cron launch my script every sunday !
      I tried that…
      00 18 8-14 * 0 if [ `/opt/Oxya/TestFDM.sh` = “0” ] ; then /etc/rc.d/sybase stop && /sbin/shutdown -r now ; fi
      … or that…
      00 18 8,9,10,11,12,13,14 * 0 if [ `/opt/Oxya/TestFDM.sh` = “0” ] ; then /etc/rc.d/sybase stop && /sbin/shutdown -r now ; fi
      … same result ! It didn’t take care of day number ! Had you already this issue ?
      Thansks !

      Reply
    6. joe on March 20, 2021 12:05 am

      I have tries to run cron job as below, but it is not running as wanted.

      * * * * * php /kunden/homepages/26/d864146585/htdocs/v-sendy/autoresponders.php

      May i know what happen? Thank you.

      Reply
      • Rahul on March 22, 2021 4:36 am

        This cron is scheduled to run on every minute. Are you getting any error?

        Reply
      • Azeem on March 23, 2021 9:35 am

        run it like below.
        echo “php /kunden/homepages/26/d864146585/htdocs/v-sendy/autoresponders.php” > /script/script.sh
        while the php must be installed on your linux system, schedule your cron as below.

        * * * * * /script/script.sh

        Reply
    7. Jitin on March 10, 2021 5:03 pm

      What is the Corn to run a job “last day of the every month”
      I tried: (30 23 28-31 * * ) but it is running for 28th 29th 30th 31st of every month
      But I need last day of every month ?? March has 31st April has 30th and Feb has 28th ??

      Reply
      • Rahul on March 16, 2021 3:58 am

        Hi Jitin,

        Try below crontab format. Change months according to your requirements:

        59 23 28-31 jan,apr,jul,oct * [ “$(date +%d -d tomorrow)” = “01” ] && /root/script.sh

        Reply
    8. Arunkumar Gali on February 9, 2021 3:33 pm

      Hi This Arun

      We have mac mini machine how to schedule weekly reboot script if have please teach me

      Thanks on advance

      Reply
    9. 'sumanta on January 22, 2021 4:21 am

      Please advise the syntax for cron to run script always except during the hours of Sunday 1:00 – Sunday 3:00.

      Reply
      • Rahul on January 23, 2021 5:45 am

        I think, you schedule two cron. First will run Monday to Saturday. Second will run on Sunday ignore specific hours:

        * * * * mon-sat script.sh
        * 0-1,3-23 * * sun script.sh

        Hope this helps you.

        Reply
        • Arunkumar Gali on February 9, 2021 3:35 pm

          Rahul please help me to schedule weekly reboot script in mac machine

          Thanks in advance

          Reply
    10. Bouzid on January 21, 2021 10:19 am

      Hi, when i try to run this command over crontab, it wil not work

      10 10 * * 5 perl /home/oracle/userreport.pl TEST >/dev/null 2>&1

      but when i try manuel in a terminal like:

      oracle@server1~] perl /home/oracle/userreport.pl TEST
      it will work

      TEST is the Databasename
      What did i do wrong!!
      thanks

      Reply
      • Rahul on January 22, 2021 1:02 pm

        Try to use full path of perl command. like:

        10 10 * * 5 /usr/bin/perl /home/oracle/userreport.pl TEST >/dev/null 2>&1

        It still not work try below:

        10 10 * * 5 cd /home/oracle && /usr/bin/perl userreport.pl TEST >/dev/null 2>&1

        Reply
    11. vilas on January 7, 2021 7:41 am

      how to cron shell script with parameter, I an execute shell script on terminal as ./test.sh username but it’s not executing through CRON.

      Note : username is parameter which read value in script.

      Reply
    12. João on December 14, 2020 2:37 am

      how to check the disk space of the root partition of the server and accumulate in the file at /home/ubuntu/test.txt. Set the command to run every hour. Use the command df -h.?

      Reply
      • Rahul on December 14, 2020 2:04 pm

        The below cron will check disk uses for /dev/sda1 every hour and store in text.txt file:

        0 * * * * df -Ph /dev/sda1 | grep -vE ‘^Filesystem|tmpfs|cdrom’ | awk ‘{ print $5 }’ > /home/ubuntu/text.txt

        Reply
    13. dinesh on December 13, 2020 7:08 am

      How to check the scheduled cron jobs between 00:00 am to 1:30 am.

      Reply
    14. Sohail on October 18, 2020 7:27 pm

      You can create anywhere in any directory, just you’ve to mentioned path where it has saved. So that it can locate.

      Reply
    15. Rohit on October 8, 2020 10:05 am

      How to run a job every alternate Sunday.
      30 08 1-7,15-20,29-31 * 0 — not working
      30 08 1-7,15-20,29-31 * sun — I am waiting for the result.

      Reply
    16. kiran on July 15, 2020 7:50 am

      Hi
      How to schedule cron to execute on last sunday of every month.

      Reply
    17. Tariqul Islam on June 26, 2020 3:17 am

      @Weekly Cron Job Example is wrong. Please correct it.
      it should be.
      0 0 * * mon ‘command here’

      Reply
      • Rahul on June 27, 2020 3:48 am

        Thanks Tariqul, Tutorial has been updated.

        Reply
    18. RAK UNGCHUSRI on June 9, 2020 4:24 pm

      Thank you for the cron document. The man page on cron was rather hard to read. Your page makes it easy to understand, especially with the 20 examples.

      Reply
    19. kishore on June 3, 2020 9:03 am

      how can we set different timings in different days in single cronjob
      eg: 5 a.m. on monday
      6 a.m. on tuesday

      Reply
      • Rahul on June 3, 2020 9:55 am

        That is not possible with cronjob, You need to handle this in your script or schedule multiple crons.

        Reply
    20. Jeremy on May 1, 2020 3:09 pm

      Recently upgraded to ubuntu 20.04, I suspect the @ functionality is broken as my @daily and @weekly jobs stopped running after upgrade. Can you confirm? Cron version 3.0pl1-136ubuntu1

      Reply
    21. Everson dos santos brunelli on March 10, 2020 2:18 pm

      Bom dia;

      Criei uma tarefa para separar as nf da pasta, porem o crontab executa e não acontece nada.
      */1 * * * * /totvs/doc/danfe/separa_danfe_na_pasta.sh

      Reply
      • Rahul on March 11, 2020 7:09 am

        Your script is scheduled to run every 1 minute. Make sure the script is working file with manually execute. Also separa_danfe_na_pasta.sh have proper execute permissions.

        Reply
        • Abu on May 12, 2020 10:38 am

          Sorry, I was wrong.
          The example is correct so it must be just a permissions issue, as Rahul said

          Reply
    22. Swapan Sutra Dhar on October 19, 2019 7:40 am

      very helpful with clear understading

      Reply
    23. Raki on September 8, 2019 12:03 pm

      Cool man. I bookmarked this page for my upcoming cron entries work reference 🙂

      Reply
    24. irfan on July 30, 2019 6:13 am

      Hi, i wonder about how can i do 9.15 and 10.20 ? is it possible to do it ?

      Reply
      • nrj on September 23, 2019 9:04 am

        15 9 * * * /usr/bin/script.sh
        20 10 * * * /usr/bin/script.sh

        Reply
    25. Mohammad on July 15, 2019 4:10 pm

      Hi Rahul,

      I want to run a job “every 10 days before the second Wednesday of the month”. Your help will be really appreciated.

      Mohammad

      Reply
    26. Rahul Kale on June 25, 2019 2:28 pm

      How to schedule the cronjob that will run whole month except one day.Like the job will run whole month but it should not run on 5th date.
      Some one will help me on this

      Reply
      • Rahul on June 26, 2019 10:10 am

        You can use the following syntax:

        0 4 1-4,6-31 * * /path/to/script.sh
        

        Here “1-4,6-31” defines the date, which will skip the 5’th of the month. Hope this helps you

        Reply
    27. Mahesh on June 5, 2019 1:16 pm

      How we can pause the cron job for two hours.? and after two hours I want to run the cron job as usual.

      Reply
    28. Mamata on May 8, 2019 11:29 am

      how to run the script for every 5 seconds using crontab??

      Reply
    29. Ashok Patidar on April 24, 2019 1:23 am

      Hi Rahul,
      Thank you o much for post cron details.
      I want to monitor cron in real time as well want to know that by which cron server CPU or RAM got full utilized or which cron not executed properly.
      Thanks

      Reply
    30. Shreya on April 12, 2019 5:53 am

      */35 * * * *, we have tried this but not working as expected. We need a job to run at every 35 minutes round the clock. In this case, first build will trigger at 4:00 (say), next build will trigger at 4:35 and the next build is getting triggered at 5:00 not at 5:10. In a single hour it is triggering twice rather going to next hour.
      The sequence for this */35 * * * * is
      4:00
      4:35
      5:00
      5:35
      6:00
      In a single hour, it is getting triggered again without completing 35 minutes. Please check once and help me to get correct one!

      Reply
      • vice on July 15, 2019 2:12 am

        try this 35 * * * *

        Reply
        • Rahul on July 15, 2019 9:51 am

          This will run at 00:35, 01:35, 02:35 etc.

          Reply
    31. Shreya on April 9, 2019 11:30 am

      How can I make a job to run at every 35 minutes around the clock? Like, 4:00,4:35,5:05,5:40 and so on

      Reply
      • Rahul on April 10, 2019 4:25 am

        Try below:

        */35 * * * * COMMAND

        Reply
    32. sudharshan on March 22, 2019 9:44 am

      what is the command to check for how many days or seconds user kept backup in a server

      Reply
    33. karterlee on February 15, 2019 1:22 am

      If i want to execute a script on 0:30 am every 10 day, which is correct?
      30 * */10 * * script.sh
      30 0 * */10 * * script.sh

      Reply
      • Rahul on February 15, 2019 12:41 pm

        Try: 30 0 */10 * * script.sh

        Reply
    34. Sagar parki on February 7, 2019 5:28 am

      Hi, I want to schedule a cron which will run every minute between to 3 – 8. Can u plz help me out.

      Reply
      • Rahul on February 7, 2019 6:43 am

        Try this: This will execute any script every minute starting 3AM to 8AM

        * 3-8 * * * /scripts/script.sh

        Hope this helps you.

        Reply
    35. dele on January 22, 2019 3:42 pm

      wow, good tutorials. Could you please cover how to save jobs to crontab. I presently have a challenge doing this on oracle linux 7.

      Reply
    36. Pravin on January 8, 2019 5:50 am

      0 2 * * * /bin/sh backup.sh

      Your first example has a problem. It won’t execute. You need to remove ‘sh’.

      Reply
    37. RK on October 24, 2018 4:18 pm

      I want to run the same job @ 2:00 AM Every day except on Wednesday. On Wednesday’s i want to run the same job @ 3:00 AM. is it possible with single line command.

      Reply
      • pr0t on January 2, 2019 6:05 am

        Try the following:

        0 3 * * 3 /path/to/your/script.sh
        0 2 * * 0-2,4-6 /path/to/your/script.sh

        Two lines in cron for the same task. It applies to your case.

        Reply
    38. Helio on September 7, 2018 6:01 pm

      Thank you very much for the time you put in creating these tutorial sir.

      Reply
    39. mukesh on May 31, 2018 5:04 am

      very good effort keep it up

      Reply
    40. Vijay on May 16, 2018 3:05 am

      Can someone help me with the below queries plz?
      How to configure a cronjob to run on alternate Sundays?
      How to configure a cronjob to run on alternate Months (example – Jan,Mar, May etc) without using the literals like 1,3,5 or jan,mar,may ?

      Reply
    41. Rak Ungchusri on May 7, 2018 8:44 pm

      Thank you for your post. Although I have used it several times but not often enough to remember the different parameters.

      Reply
    42. Dave on March 14, 2018 7:27 pm

      Those are likely sh or bash scripts, but can be any program. You must specify the full path to the program, and any args if the program takes args.
      Also be aware that cron does run as the user, but does not go through the normal user login sequence. Therefore, you must specify full paths to any commands within your shell scripts because they might not be in the PATH that is defined for the user at login. For example, a script that runs curl (from /usr/bin/curl) might work when I am logged in as user=dave, but from cron the script might not have /usr/bin in the PATH so it wouldn’t find curl. So in the script you would specify /usr/bin/curl instead of just curl. (This also means if your script uses an alias defined at login, cron won’t know about the alias)

      Reply
    43. NewTechy on December 6, 2017 12:08 pm

      This is the answer I am looking for after have been searching from many sites!! Thanks.

      Reply
    44. srimanta on December 4, 2017 7:17 am

      Thanks for the guide..very nicely crafted…

      Reply
    45. Steve Williams on October 6, 2017 3:47 pm

      Rahul, thanks for your guide. That’s clear & concise!

      Reply
    46. Leslie Satenstein on August 13, 2017 4:20 am

      #To schedule something that runs every two minutes
      */2 * * * * DO_THIS_COMMAND_EVERY_TWO_MINUTES
      * */3 * * * Do This_Command_every_three_hours

      Reply
      • Rahul K. on August 14, 2017 9:56 am

        Hi Leslie. The second cron have some issues. You need to specify minute to run. For example.

        0 */3 * * * Do This_Command_every_three_hours

        Now, this will like 3:00, 6:00, 9:00 and so on.

        Reply
    47. Unknown on May 5, 2017 3:21 pm

      Very Useful

      Reply
    48. pan on January 3, 2017 2:33 am

      for ex. 8:
      0 2 * * sun [ $(date +%d) -le 07 ] && /script/script.sh

      can you do it with
      0 2 1-7 * sun /script/script.sh

      Reply
    49. raj on July 16, 2016 9:56 am

      I think day of week should be 0 to 6

      Reply
      • vader on July 22, 2016 6:54 am

        both 0 and 7 mean SUN

        Reply
    50. Gibies George on June 26, 2016 2:49 am

      Thank you very much for the information.

      Very nice article.

      Reply
    51. ramarasan.manickam on August 20, 2015 10:57 am

      Nice Post

      Good work and keep it up

      Thanks for your knowledge support 🙂

      Reply
    52. Roberto on December 22, 2014 3:33 pm

      How to start X applications from CRON ???

      Reply
    53. Gareth on November 13, 2014 6:53 am

      Very nice article.
      Only one thing that I do not get. You keep on talking about scripts.sh etc…..
      How does someone make these scripts, where are they and where do you save them etc…

      Thanks for the information, brilliant article.

      Reply
    54. 2013james on March 30, 2013 6:56 am

      There is an interactive cron simulator at http://www.dataphyx.com where these examples, and any other combinations of crontab timing parameters, can be tried out off-line. Time/date values go in, a list of job run-times comes out.

      Reply

    Leave A Reply Cancel Reply

    Advertisement
    Recent Posts
    • Linux: A Guide to Extracting Lines Between Matching Patterns
    • How to Setup PHP, MySQL, and Nginx Using Docker Compose
    • Enabling TLS 1.3 on Windows Server: A Step-by-Step Guide
    • Restricting Users from Running `chmod 777`
    • How to Set Up Laravel with Dockerfile and Docker-Compose
    Facebook X (Twitter) Instagram Pinterest
    © 2024 Tecadmin.net. All Rights Reserved | Terms  | Privacy Policy

    Type above and press Enter to search. Press Esc to cancel.