On Mon, 2006-09-11 at 09:35 +0200, stephan beal wrote:
It was a space, i've replaced it with a tab, but that doesn't make a difference (as it shouldn't). Vixie cron isn't as picky as Solaris cron.
My crontab low looks like:
SHELL=/bin/bash MAILTO=stephan 32 9 * * * /space/backups/navigating-backups
(That's a tab between fields 5 and 6)
And i get no mail, no output, no nothing. It's simply ignoring the cron job. The very minimal output should be something like "nothing to do", because the script is just running a makefile which might determine that all targets are up to date.
Looking through last month's archives on this list, someone else had a similar problem and no solution was every proposed. It looks like i'm going to have to start, as a workaround, using 'at' jobs which automatically reschedule themselves after running.
I had a similar problem. On Sept. 3, I started a thread titled: "Cron Not Running Tasks". Someone sent me something to check (although I don't see it within the thread itself). They stated that if you change a crontab, cron needs several minutes before recognizing the change. As it turned out, that was my problem. I recently came over from Debian Linux. I was used to being able to change a time in a crontab to within a minute of the current time. It would run with no problem. With SuSE, changing the run time of a task to a time so close in the future would cause cron to not run the job at all. Perhaps you are doing this as well? Try changing the time for a task to something 10 or 15 minutes in the future and see if the cron daemon runs it then. It solved my problem. Cron is happily running my crontab tasks. Rick -- Rick's Law: What cannot be imagined will be accomplished by a fool. PGP Key Id: 9E1125E0