In what cases will anacron not run?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












I am trying to understand how anacron works (in Fedora). I have three related questions. I am confused because of the following statement from the anacrontab manual:




The START_HOURS_RANGE variable defines an interval (in hours) when scheduled jobs can be run. In case this time interval is missed, for example, due to a power down, then scheduled jobs are not executed that day.




The first, main question is: What does the phrase "time interval is missed" mean?



I am aware that there are software clock and hardware clock, and that the software clock depends on the hardware clock. As I understand, if the power is down long enough, then after booting the system, the hardware clock has to be adjusted from the software clock, therefore the software
clock has to be adjusted independently (manually or automatically).



So, here comes the second question: Does it mean that if anacron should have been run in the time that the system was down, and after booting – in the time anacron was running – it was still not having proper time, then anacron was thinking that it is not yet the time to run (and therefore it will not run)?



I realise that anacron is not a daemon itself, as stated in this stackexchange answer. As the Fedora documentation on anacron states, the anacron jobs are run by the crond daemon. Also, is states that the anacron jobs will be run as soon as the system is up.



So, here comes the third question: If the answer for the second question is "yes", then could the system time be adjusted before crond run anacron, and therefore anacron will run however (because at that time the time will be correct)?









share



























    up vote
    0
    down vote

    favorite












    I am trying to understand how anacron works (in Fedora). I have three related questions. I am confused because of the following statement from the anacrontab manual:




    The START_HOURS_RANGE variable defines an interval (in hours) when scheduled jobs can be run. In case this time interval is missed, for example, due to a power down, then scheduled jobs are not executed that day.




    The first, main question is: What does the phrase "time interval is missed" mean?



    I am aware that there are software clock and hardware clock, and that the software clock depends on the hardware clock. As I understand, if the power is down long enough, then after booting the system, the hardware clock has to be adjusted from the software clock, therefore the software
    clock has to be adjusted independently (manually or automatically).



    So, here comes the second question: Does it mean that if anacron should have been run in the time that the system was down, and after booting – in the time anacron was running – it was still not having proper time, then anacron was thinking that it is not yet the time to run (and therefore it will not run)?



    I realise that anacron is not a daemon itself, as stated in this stackexchange answer. As the Fedora documentation on anacron states, the anacron jobs are run by the crond daemon. Also, is states that the anacron jobs will be run as soon as the system is up.



    So, here comes the third question: If the answer for the second question is "yes", then could the system time be adjusted before crond run anacron, and therefore anacron will run however (because at that time the time will be correct)?









    share

























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I am trying to understand how anacron works (in Fedora). I have three related questions. I am confused because of the following statement from the anacrontab manual:




      The START_HOURS_RANGE variable defines an interval (in hours) when scheduled jobs can be run. In case this time interval is missed, for example, due to a power down, then scheduled jobs are not executed that day.




      The first, main question is: What does the phrase "time interval is missed" mean?



      I am aware that there are software clock and hardware clock, and that the software clock depends on the hardware clock. As I understand, if the power is down long enough, then after booting the system, the hardware clock has to be adjusted from the software clock, therefore the software
      clock has to be adjusted independently (manually or automatically).



      So, here comes the second question: Does it mean that if anacron should have been run in the time that the system was down, and after booting – in the time anacron was running – it was still not having proper time, then anacron was thinking that it is not yet the time to run (and therefore it will not run)?



      I realise that anacron is not a daemon itself, as stated in this stackexchange answer. As the Fedora documentation on anacron states, the anacron jobs are run by the crond daemon. Also, is states that the anacron jobs will be run as soon as the system is up.



      So, here comes the third question: If the answer for the second question is "yes", then could the system time be adjusted before crond run anacron, and therefore anacron will run however (because at that time the time will be correct)?









      share















      I am trying to understand how anacron works (in Fedora). I have three related questions. I am confused because of the following statement from the anacrontab manual:




      The START_HOURS_RANGE variable defines an interval (in hours) when scheduled jobs can be run. In case this time interval is missed, for example, due to a power down, then scheduled jobs are not executed that day.




      The first, main question is: What does the phrase "time interval is missed" mean?



      I am aware that there are software clock and hardware clock, and that the software clock depends on the hardware clock. As I understand, if the power is down long enough, then after booting the system, the hardware clock has to be adjusted from the software clock, therefore the software
      clock has to be adjusted independently (manually or automatically).



      So, here comes the second question: Does it mean that if anacron should have been run in the time that the system was down, and after booting – in the time anacron was running – it was still not having proper time, then anacron was thinking that it is not yet the time to run (and therefore it will not run)?



      I realise that anacron is not a daemon itself, as stated in this stackexchange answer. As the Fedora documentation on anacron states, the anacron jobs are run by the crond daemon. Also, is states that the anacron jobs will be run as soon as the system is up.



      So, here comes the third question: If the answer for the second question is "yes", then could the system time be adjusted before crond run anacron, and therefore anacron will run however (because at that time the time will be correct)?







      linux fedora cron anacron





      share














      share












      share



      share








      edited 1 min ago

























      asked 8 mins ago









      silv

      215




      215

























          active

          oldest

          votes











          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "106"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          convertImagesToLinks: false,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













           

          draft saved


          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f475712%2fin-what-cases-will-anacron-not-run%23new-answer', 'question_page');

          );

          Post as a guest



































          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes















           

          draft saved


          draft discarded















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f475712%2fin-what-cases-will-anacron-not-run%23new-answer', 'question_page');

          );

          Post as a guest













































































          Popular posts from this blog

          How to check contact read email or not when send email to Individual?

          Displaying single band from multi-band raster using QGIS

          How many registers does an x86_64 CPU actually have?