Jobs scheduled to run between 1 and 2 am get run twice when the machine in
question is in the Pacific timezone. I don't believe that this is correct
behavior.
While there is certainly a workaround (don't schedule jobs between 1 and 2 am),
many end-users will have their own crontabs, and may not realize this.
Package: cron
Version: 3.0pl1-72
Jobs scheduled to run between 1 and 2 am get run twice when the machine in
question is in the Pacific timezone. I don't believe that this is correct
behavior.
While there is certainly a workaround (don't schedule jobs between 1 and 2 am),
many end-users will have their own crontabs, and may not realize this.
M