Scott Leighton wrote:
On Friday 07 April 2006 3:29 am, Joachim Schrod wrote:
Scott Leighton wrote:
cron monitors directory timestamp of /etc/cron.d and /var/spool/cron/tabs and the file timestamp of /etc/crontab. This is explained in the man page of cron, in the 3rd paragraph.
Empirical evidence says the man page is incomplete.
No, it is complete, as mentioned by Carlos. One addition to what he said, for the sake of searches in the archives:
cron does not monitor /etc/cron.{daily,hourly,monthly}. These scripts are executed by /usr/lib/cron/run-crons which is called in /etc/crontab every 15 minutes.
run-crons tests for the presence of lockfiles, it has nothing to do with the cached scripts that crond is dealing with.
SUSE 10.0, /usr/lib/cron/run-crons: From line 73 to line 100, lock files are deleted, as you write. Line 114-165 defines the shell function run-scripts that is called in line 187. Alas, /usr/lib/cron/run-crons runs the scripts from those directories, this is _not_ done by crond itself. That script also does this a bit more intelligently than crond with /etc/cron.d/*, actually; as it ignores obvious backup files and rpm files. Cheers, Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany