Quote:
|
Originally Posted by jbarley If the scripts were run automatically on their default schedule, their date stamps would vary and their time stamps would indicate executions between 03:15 and 05:30 hours. |
The times of execution could be any time, depending on when the computer was first awakened after the script was supposed to run.
Here's mine from today:
-rw-r--r-- 1 root wheel 394469 Feb 25 09:34 /var/log/daily.out
-rw-r--r-- 1 root wheel 1579 Feb 1 12:52 /var/log/monthly.out
-rw-r--r-- 1 root wheel 9415 Feb 25 09:41 /var/log/weekly.out
You can see the times were around 9:30 this morning (right around the time I awoke the computer), and those scripts were run automatically without the need for me to force them to run with 3rd-party software or via a command-line command.
I'm stickin' to my guns and saying that 3rd-party software to run the daily/weekly/monthly cron scripts is useless, since they get run automatically the first chance the system has to run them. Running them twice (once automatically by the system, once again by the user forcing the running of them) is not beneficial at all. Running them manually is also pointless.
If the scripts are not running by themselves without user interaction, then that would indicate a deeper problem. In this case, using 3rd-party software or running the scripts manually is simply a band-aid, and a better course of action would be to hunt down the problem that is preventing them from running automatically.