On Sunday 27 November 2005 15:43, Carlos E. R. wrote:
The Sunday 2005-11-27 at 13:53 +0100, I wrote:
I have just now edited /usr/lib/cron/run-crons:
#cron.daily) TIME="-ctime +1 -or -ctime 1" ;; #cron.weekly) TIME="-ctime +7 -or -ctime 7" ;; #bug cron.daily) TIME="-cmin +1400 -or -cmin -1400" ;; cron.weekly) TIME="-cmin +10080 -or -cmin -10080" ;;
and I'll see if that fixes the 15' delay.
[...]
Well, it is not correct. It ran within 15 minutes of editing /usr/lib/cron/run-crons, even if the flag file was stamped "Nov 27 01:15 cron.daily":
Nov 27 01:15:02 nimrodel run-crons[15358]: Starting cron daily run Nov 27 14:00:01 nimrodel run-crons[20757]: Starting cron daily run
I'll touch the flag file and see what happens:
nimrodel:~ # touch --date="today 01:15:00"
Note that touch doesn't set the ctime, just the mtime, so this won't have any effect.
/var/spool/cron/lastrun/cron.daily nimrodel:~ # l /var/spool/cron/lastrun/cron.daily -rw-r--r-- 1 root root 0 Nov 27 01:15 /var/spool/cron/lastrun/cron.daily
[...]
No! It is running again at 14:30. I think I will undo the changes to the script, it is wrong: it is running every fifteen minutes:
Nov 27 01:15:02 nimrodel run-crons[15358]: Starting cron daily run Nov 27 14:00:01 nimrodel run-crons[20757]: Starting cron daily run Nov 27 14:15:01 nimrodel run-crons[21710]: Starting cron daily run Nov 27 14:30:02 nimrodel run-crons[22550]: Starting cron daily run
This looks strange. Did you remove the section of run-crons which deletes the spool file? Or did you put the line that outputs this message in the wrong place, so it gets printed every time run-crons runs instead of when cron.daily runs?