Hi Josip, Josip Rodin wrote: > Hi, > > I believe this problem just hit me too, on lenny. The issue here is that > cron will skip the execution of ALL jobs in a particular /etc/cron.d/file > if just one of them has an incorrectly formatted timing specification.
Yes, this is intentional. > In my case I had made a typo in the day-of-month field and entered "38" > instead of "28". This was *not* actually reported anywhere, or at least > not anywhere I could see it, I only found it after manual inspection. Errors such as these are logged to syslog, eg: Apr 23 00:03:01 test cron[11556]: Error: bad hour; while reading /etc/cron.d/foo > As soon as I fixed that, the other job in the same file that runs > every fifteen minutes was magically reactivated. I added another log message to the processing code which explicitly states that the entire crontab will be disabled if it contains errors. Christian
signature.asc
Description: OpenPGP digital signature
