Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

The clocks went back an hour last night at 2am - British Summer Time ended. My backup job is scheduled to run daily at 01:12. It ran twice. This is on a Debian Lenny server.

man cron says:

if the time has moved backwards by less than 3 hours, those jobs that fall into the repeated time will not be re-run

The crontab entry is: 12 1 * * * /home/lawnjam/bin/

What's going on?

share|improve this question

Ah, turns out it's a Debian bug.

Fixed in cron 3.0pl1-109, but Lenny is still on 3.0pl1-105.

share|improve this answer
First reported in 2003! That's a speedy fix... – hmallett Oct 31 '10 at 12:45
That's why I never schedule any cron jobs to run between 1am and 3am. Glad to see this bug will be gone in Debian Squeeze. – Steven Monday Oct 31 '10 at 15:27

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.