an easier way to determine if cron is actually running, is via “rccron status”, executed as root
Any output generated by cron jobs is usually sent via email to the owning user of the cron tab, in your case that should be the root user. Anything to find there, in addition to any messages in syslog (grep CRON /var/log/messages) as asked by Hans?
A simple test entry could be
The time stamp of /tmp/cron.lastrun should follow the current time, verified by “ls -l /tmp/cron.lastrun”.
Do the status files of cron.daily etc suggest that cron is actually doing something, by displaying an appropriate (current) time stamp?
[QUOTE]# ls -l /var/spool/cron/lastrun/
-rw-r–r-- 1 root root 0 Feb 13 13:15 cron.daily
-rw-r–r-- 1 root root 0 Feb 7 16:00 cron.weekly[/QUOTE]
The first job runs well, everyday at 8.45am. But the second job doesn’t
The permissions on /oracle/SID/sch_jobs are 777 so that is not an
Is it safe to assume that you waited another hour for the second job to
run, and that after that hour had elapsed the system was still on and in
the same state as it was when the first job ran? Why not have them set to
the same time for a better test?
ls: cannot access /tmp/cron.lastrun: No such file or directory[/QUOTE]
What does “grep cron /var/log/messages” report (if your host’s syslog is redirected somewhere else, search that destination, of course )? For each invocation you should usually see an according message similar to
Mar 4 11:00:01 yourhost /usr/sbin/cron: (root) CMD (/usr/bin/touch /tmp/cron.lastrun)
and the invocations of “crontab -l” should leave their traces there, too.
If you “see” your cron jobs once per minute, does your root user receive any error mails concerning the invocations - as “ls” doesn’t show any result (while cron seems to run, according to i.e. syslog and /var/spool/cron/lastrun/), some error then must have occurred…